Hi @Irshad Ahmad Fareq
In addition to the points provided by @Andreas Baumgarten , i would like to add a few more:
First, make sure that you know the exact port aaPanel is using and that the service is running correctly on the VM and log into your VM via SSH. You can find the port using the aaPanel by using the below command:
sudo bt 14
The above command usually displays panel information, including the access address and port and the default is mostly 7800 or 8888, but you might have changed it. so, please verify it once.
Kindly verify that the service is actively listening on that port for all network interfaces, not just localhost (127.0.0.1), you can use the below command to check it:
sudo ss -tulnp | grep ':<PORT>' #OR sudo netstat -tulnp | grep ':<PORT>'
Replace <PORT> with your actual aaPanel port number and if it's listing you will see 0.0.0.0:<PORT> or else *:<PORT> or if it only shows 127.0.0.1:<PORT>, aaPanel itself is configured incorrectly to only listen locally.
Kindly verify the NSG:
Go to your VM > Settings > Networking > Inbound port rules > Click Add inbound port rule.
Configure the rule:
- Source: Any
- Source port ranges: *
- Destination: Any
- Service: Custom
- Destination port ranges: Port number aaPanel is using.
- Protocol: TCP
- Action: Allow
- Priority: Choose a number. Lower numbers have higher priority. Make sure it's lower than any general deny rules that might conflict.
- Name: Give a name and click on add.
Kindly re-verify that you are using the correct Public IP address listed on the Azure VM's Overview page and make sure that you are accessing it correctly in your browser: http://<YOUR_PUBLIC_IP>:<PORT> or https://<YOUR_PUBLIC_IP>:<PORT> (if SSL is enabled).
Kindly test connectivity from different compute (not the VM) by using telnet: telnet <YOUR_PUBLIC_IP> <PORT>
Kindly let us know if the above helps or you need further assistance on this issue.