-1

The instance is a Windows Server 2016. It runs an Apache server (for the ports 80 and 443), and a GlassFish server (on ports 8080 and 8181). On the machine itself, everything seems to work fine when I invoke localhost:.

I mapped the public IP of the instance to a DNS. When I invoke it with the Apache's ports it works fine, but not with the GlassFish ports. Same result when I use the public IP as well.

I tried to configure the Virtual host parameter directly from the GlassFish console (localhost:4848) and also the solution in here, without success. What am I missing here?

2
  • 1
    Does your firewall allow connections on ports 8080 and 8181 from outside of your server? It looks like it doesn't, if you're not able to connect even with the IP address. You don't need any special virtual host configuration in GlassFish if you only want to serve a single DNS domain. Commented Oct 12, 2023 at 22:01
  • I added a Firewall inbound rule exclusively for those 2 ports, but that did not help. But by reading you, I insisted a bit more on the firewall side of things. And I could finally make it work by disabling the Private Profile. Thanks for the hint! Commented Oct 13, 2023 at 4:04

1 Answer 1

0

It was a firewall issue. Although I added inbound rules to allow for ports 8080 and 8181 explicitly, this wasn't enough.

I had to check a bit more (following the hint of @OndroMih in the comments of the post), and by disabling some sections of the firewall, it appeared that the Private Profile was the blocking one. Hence I disabled it.

Not sure what are the implications of that, but it solves my problem for now.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.