Thanks for the clarification about connections. Actually I used iptables to filter the ports. To remove the filter you can use "sudo iptables -F". Anyway this should not be the reason why the system is unreacheable. In case there Is a problem with hydrosys4, normally you should get a "bag gateway" message in the browser which is sent by nginx that is acting as reverse proxy. Anyway I suggest to see if the hydrosys4 starts manually using shh so you can see the logs. Login with SSH, type "sudo killall python3", this command should not provide answer, if it says no python process, then there is an issue with the SW. Then go to the folder "cd env/autonom" then type "sudo python3 bentornado.py" you should see the program starting. If there is an issue we should be able to see

Hi,

The web browser is not opening the page on port 5172.

I have not connected it to my WiFi. It is connected via an Ethernet cable from the RPI to my LAN Switch.

Even when I connect to the Hydrosys4 WiFi AP I am facing the same issue where only Port 22 is responding.

I am using PUTTY Client to connect via SSH and i am able to login to the SSH of the RPI... pasting below the "ifconfig" details on the RPI device...

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.2  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::856:5d20:6e3e:e16  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:be:a4:2a  txqueuelen 1000  (Ethernet)
        RX packets 27415  bytes 1727880 (1.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 26756  bytes 1841181 (1.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1448  bytes 91797 (89.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1448  bytes 91797 (89.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.172  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::5364:5142:9e3d:7cd8  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:eb:f1:7f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30  bytes 4826 (4.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

The ETH port is receiving the IP from the network DHCP as there is an Ethernet cable between them as told previously.

The WLAN0 port is having the default IP which the Hydrosys4 system is having.

Strangely even PING to any of the above IP address is not getting any replies....

C:\>ping 192.168.1.172

Pinging 192.168.1.172 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.172:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>

Is there any broken files in the system which are only allowing me to communicate with Port 22 of SSH ???

This is a very strange thing I am seeing in my 25+ years of Networking Communications :-) where only Port 22 is responding and all other on the same system don't.

I require more info about your system otherwise it is impossible to help. What is the error you get on the web browser? Is it time out or other reasons? Is the hydrosys4 configured to connect with you WiFi network? If yes, it will first start as WiFi AP, then connect to the WiFi network after 3 minutes. So you have to be careful about timing. If you are able to access the system using SSH, can you explain how you do?

Hi,

I tried using WiFi where the RPI is connected via Ethernet cable to the Wifi Network the issue is there.

Also when I connect directly to the Hyrdosys Wireless AP I am facing the same issue.

When I ping the IP address of the RPI it responds but the I get no response on the HTTP port via webbrowser.

This is the first time I am facing this peculiar problem and it has never happened before.

I connected to the Hydrosys4 inbuilt WiFi AP and I was leased an IP address 192.168.1.181

But when I try to connect or ping to 192.168.1.172 ...... I am getting no response.

So I ran a entire NMAP scan on the full range from 192.168.1.1 - 192.168.1.254 to see what is alive on the network and I got the following results:

Starting Nmap 7.92 ( https://nmap.org ) at 2022-03-26 09:16 India Standard Time
Nmap scan report for 192.168.1.172

Host is up (0.014s latency).

All 100 scanned ports on 192.168.1.172 are in ignored states.
Not shown: 100 filtered tcp ports (no-response)
MAC Address: B8:27:EB:EB:F1:7F (Raspberry Pi Foundation)

Nmap scan report for 192.168.1.181
Host is up (0.00066s latency).
Not shown: 94 closed tcp ports (reset)
PORT     STATE SERVICE
135/tcp  open  msrpc
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
5357/tcp open  wsdapi
7070/tcp open  realserver
9999/tcp open  abyss

Nmap done: 254 IP addresses (2 hosts up) scanned in 34.83 seconds

This is showing that 192.168.1.172 is alive but it's not responding to any ports.

Hello there, About the IP connection, do you use WiFi? The fact that there is no ping answer can indicate a connection problem or change in IP address. For the SSH you said it is working, but do you access using the same WiFi connection or using a cable? With SSH it is possible to use several commands to see the network as for example ifconfig gives some basic info. Second consideration, did you make any configuration change withing the hydrosys4 or in the network before this problem happen?