new https listener not working

[Jose Luis Romero]

I created a new https listener (for Letsencrypt cert) at port 8282, it is enabled and security=true, added the Certificate NickName and key store but when I try to access my apps through it, nothing happens, like the listener doesn't exist. the router forwarding for 8282 is configured too

I tried this on the default http-listener-2 and it works, the LetsEncry cert is recognized and browsers show it as "secure", I just created a new listener and put all the config there

What am I doing wrong? what am I missing

payara 5.201

[Ar Fernando]

Hello Jose,

Any reason that you are using port 8282? Can you please try 4443. Then see whether you can listen at port 4443.
If you are using Linux then check the SELinux status, e.g. sestatus. Try making SELinux "permissive" mode to see whether you can listen at port 4443.
If it is on Windows I will try disabling the firewall to test.

Good Luck!

[Jose Luis Romero]

I am on Windows 10, I didn't touch the firewall (I didn't have to) I finally made it works, I found an old issue on Github about a bad creation of the new listeners in domain.xml, after a lot of manual modifications (at some point no listener were even working), at last, I created the listener from Network Listener instead of Http Listener, which essentially seems the same but finally worked, the bug seems to be in the tag virtual-server, the new httpslistener wasn't added

<http-service>

        <access-log></access-log>

        <virtual-server network-listeners="http-listener-1,http-listener-2,https-letsencrypt" id="server"></virtual-server>

        <virtual-server network-listeners="admin-listener" id="__asadmin"></virtual-server>

</http-service>