Hey Victor,
It's nice to know someone else in the world is working on this too. LoL This is giving me trouble and I want to get this working ASAP. :-)
Are you saying is it possible that another service (outside of the GLUU container) is using the port or ports that GLUU is using--and causing a problem?
I was paranoid about this so I tried to make everything simple and vanilla before I troubleshooted the GLUU stuff. Outside of the GLUU server, I did the following:
1) Stopped the http service
2) Stopped the tomcat service (if installed)
3) Stopped the iptables service
4) Changed selinux to permissve (check by typing the command: sestatus )
5) Open the ports on the network
6) Test that the sever is resolvable by IP address and DNS
This is working reliably for me.....except when the IP and DNS information change (if you are using Amazon Web Services-AWS like me) you have the deal with the problems that come up with the GLUU server's apache settings. (what I'm dealing with at this moment). I think it is related to the httpd.conf file and the .conf files for the virtual hosts that are also setup. I am not that familiar with virtual hosts on an apache server. I'm still not sure if the client should be on the same machine as the GLUU server, but according to this post it should not:
https://support.gluu.org/view/installation/help-with-dynamicconf-in-mod_auth_oidc-apache-plugin/2161
I'll see what I can work out and post back my findings.
Cheers,
Adrian