Hi xxx,
I'm sorry, I thought the port 3000 is available for outbound connections, but it is indeed blocked by an SElinux policy that's in place.
I don't have a complete list of allowed ports for outbound connections, but here's a list of SElinux labels that specify opened ports on OpenShift Online per the current configuration:
61pki_ca_port
amqp_port
commplex_port
flash_port
ftp_port
generic_port
git_port
http_cache_port
http_port
ircd_port
jabber_client_port
jacorb_port
jboss_debug_port
jboss_management_port
jboss_messaging_port
memcache_port
mongod_port
mssql_port
munin_port
mysqld_port
oracle_port
pki_ra_port
pop_port
postgresql_port
pulseaudio_port
smtp_port
soundd_port
ssh_port
virt_migration_port
whois_port
You've tested this on the gear using curl, which returned 'permission denied' rather than 'connection refused', indicating that it's denied by a local policy not blocked by the remote server.
You can also test the port availability using telnet, but please make sure not to do that programatically in rapid succession. Scanning open ports will surely be detected and the account may be blocked.
Best regards,
Jiri
OpenShift Customer Success Team
OpenShift Online by Red Hat, Inc.