This error should not occur when using APEX Service or APEX on Autonomous Database. However, in other environments where
you need to manually configure whih outbound network requests are allowed, you can run the following script
as SYS or another user with DBA privileges to grant the appropriate privileges for the APEX engine to
use the REST APIs involved in securely delivering notifications to subscribed users.
-- Run as SYS or DBA user
declare
l_principal varchar2(20) := apex_application.g_flow_schema_owner;
l_proxy varchar2(100) := null; -- e.g. 'proxy.example.org'
l_proxy_port number := 80;
l_hosts apex_t_varchar2 := apex_t_varchar2(
'*.push.apple.com',
'*.notify.windows.com',
'updates.push.services.mozilla.com',
'android.googleapis.com',
'fcm.googleapis.com');
procedure add_priv(p_priv varchar2, p_host varchar2, p_port number) is
begin
dbms_network_acl_admin.append_host_ace (
host => p_host,
lower_port => p_port,
upper_port => p_port,
ace =>
xs$ace_type(privilege_list => xs$name_list(p_priv),
principal_name => l_principal,
principal_type => xs_acl.ptype_db));
end;
begin
if l_proxy is not null then
add_priv('connect',l_proxy,l_proxy_port);
end if;
for j in (select column_value as hostname from table(l_hosts)) loop
add_priv('connect',j.hostname,443);
end loop;
commit;
end;
For more information, read this documentation chapter.