By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Port remains closed on LightSale VM (inspite of Firewall Rule being present)

0

On my new Lightsale VM, I am trying to install an application (Mailstore Server) that requires port 80 to be open. Port 80 is configured as default but attempts to connect with a tool like the following one fails with "port 80 closed".

https://www.yougetsignal.com/tools/open-ports https://portchecker.co/checking

I have tried removing the rule, and adding it again, but the port remains closed and the application installation fails because of it.

I cannot reach out to Support as I am trialling this on the Basic License. This will be a deal-breaker if I cannot get it working.

Interestingly, I am able to RDC onto the Server, so the default firewall rule for 3389 is working okay! Just not port 80.

Any ideas anyone?

Topics
Compute
Tags
Amazon Lightsail
Language
English
SLatimerBoyce
asked 10 months ago217 views
2 Answers
0

Is the Lightsail OS Windows?
If the firewall settings in the following document for Lightsail are OK, you may want to check your Windows firewall settings.
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/understanding-firewall-and-port-mappings-in-amazon-lightsail

Otherwise, check to see if Lightsail is listening on port 80 in the first place.
For example, the following command can be executed at the command prompt to check if port 80 is in use.

netstat -nao | find "80"
profile picture
EXPERT
Riku_Kobayashi
answered 10 months ago
  • SLatimerBoyce
    10 months ago

    Thanks for the speedy reply Riku. Yes the Lightsail OS is Windows Server 2022 Standard. The Firewall settings are okay as I am trying to use one of the defaults (HTTP - TCP - 80 - all IP addresses).

    When I run the above netstat command, I get this:

    Microsoft Windows [Version 10.0.20348.1787] c:\users\Administrator\netstat -nao | find "80"

    TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 1180 TCP [::]:49667 [::]:0 LISTENING 1180 TCP [{Ipv6 address} [2001:{macaddress]:80 TIME_WAIT 0 UDP 127.0.0.1:64919 127.0.0.1:64919 1180

    see here for screenshot: https://www.screencast.com/t/p29AhyDI4

    It appears the only reference to port 80 is against the MAC address, and that states "TIME_WAIT".

    I dont understand these results, or why port 80 remains closed on this new Lightsale Windows Server?

  • Riku_Kobayashi EXPERT
    10 months ago

    At any rate, I've found that it's not the firewall as the cause of my inability to connect. It appears that port 80 is not listening well. I'm not very familiar with MailStore Server, but I'm wondering if there is a problem with the configuration.

  • Riku_Kobayashi EXPERT
    10 months ago

    Is this explanation relevant? I thought that access via HTTP was not supported. https://www.mailstore.com/en/products/mailstore-server/changelog/

    This release fully removes the support for establishing unencrypted connections to MailStore Server. This also includes the HTTP-to-HTTPS redirect option, which must be considered insecure without the use of properly configured HTTP Strict Transport Security (HSTS).

0

Thanks for the responses everyone. I resolved this by creating a new Instance, this time using a build of Server 2019. The setup of Mailstore on this OS was text-book (ports were opened successfully during the install and the application installed without issue). Incidentally, I tried resetting Windows Defender back to defaults on the original Server 2022 and this took the instance down completely! Thereafter I was unable to connect to it at all (received the error "remote server has closed the connection because your instance is taking too long to respond"). Stopping and starting the VM made no difference, so I trashed it and plan to stick with 2019 instead.

SLatimerBoyce
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content