All,
I issued a "setbool http_can_network_connect=1" command and "Poof"
everything started working fine.
Thanks to all who responded for pointing me in the right direction.
Alexander Bokovoy suggested that since we have a proxy, I should
possibly restrict access to wildfly connects to come from the proxy on
the local host.
I think pboy was thinking the proxy would serve as a load balancer and
as a way to serve requests via a second wildfly instance if the first
instance is down. I am reading between the lines and thinking he
(pboy) was assuming the wilfly instances would reside on separate
servers, but perhaps I am assuming too much. Pboy, any input would be
welcome.
John
On Sat, 2023-08-19 at 23:27 +0200, Emmanuel Seyman wrote:
* John W. Himpel [18/08/2023 16:29] :
>
> Any suggestions on fixing this problem would be greatly
> appreciated.
As Alexander suggested, I suspect your issue is due to the SELinux
boolean httpd_can_network_connect.
You can run the command "/usr/sbin/getsebool
httpd_can_network_connect"
to get the current value (this is off by default).
In your case, this should be on so you'll need to run the command
"setsebool -P httpd_can_network_connect on" and your ansible playbook
will need to do the equivalent using ansible's selinux module.
I'm not sure if this is needed if Wildfly is listening only on the
localhost interface (which I would seriously recommend).
Emmanuel
_______________________________________________
server mailing list -- server(a)lists.fedoraproject.org
To unsubscribe send an email to server-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue