ERR_CONNECTION_TIMED_OUT

[KILLERMANTV]

Hello,
When i try to connect to sinusbot through chrome i get this error ERR_CONNECTION_TIMED_OUT
I tried to reinstall sinusbot but still it's not working.
With service sinusbot status it is active (running).
I disabled firewall with sudo ufw disable and added rules to firewall for port 8087.
Any ideas how to fix?

 

[mrtheo]

Same problem

 

[mxschmitt]

READ ME BEFORE YOU POST
Check the logs. ERR_CONNECTION_TIMED_OUT means, that the bot is not running^^

 

[KILLERMANTV]

It is running, service sinusbot status says that clearly.

 

[Tuetchen]

maybe running but obviously not accessable with the used adress/port combination. So yeah try to connect with the local machine to exclude external connection problems first.

 

[KILLERMANTV]

Local connection works. But when i try to connect from another machine it won't work.

 

[Multivitamin]

Can you check the output of netstat -tulpn , which ports are being used or if they are bound to a local port? Also provide us with information if the machine is in your lan and if you are connecting from a network which is able to connect, maybe a router which blocks? And check if you use the right ip address

 

[KILLERMANTV]

These ports are used by sinusbot:

tcp        0      0 127.0.0.1:40863         0.0.0.0:*               LISTEN      6389/sinusbot
tcp6       0      0 :::8087                 :::*                    LISTEN      6389/sinusbot

I am running ubuntu 16.04 in my lan, idk if router blocks it, i was using the right ip in chrome when connecting.

 

[KILLERMANTV]

Here is full list.

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      1127/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1100/sshd
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      944/cupsd
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      1536/master
tcp        0      0 127.0.0.1:40863         0.0.0.0:*               LISTEN      6389/sinusbot
tcp6       0      0 :::22                   :::*                    LISTEN      1100/sshd
tcp6       0      0 :::8087                 :::*                    LISTEN      6389/sinusbot
tcp6       0      0 ::1:631                 :::*                    LISTEN      944/cupsd
tcp6       0      0 :::25                   :::*                    LISTEN      1536/master
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           898/avahi-daemon: r
udp        0      0 127.0.1.1:53            0.0.0.0:*                           1127/dnsmasq
udp        0      0 0.0.0.0:68              0.0.0.0:*                           1115/dhclient
udp        0      0 192.168.0.157:123       0.0.0.0:*                           5339/ntpd
udp        0      0 127.0.0.1:123           0.0.0.0:*                           5339/ntpd
udp        0      0 0.0.0.0:123             0.0.0.0:*                           5339/ntpd
udp        0      0 0.0.0.0:45638           0.0.0.0:*                           1127/dnsmasq
udp        0      0 0.0.0.0:631             0.0.0.0:*                           1001/cups-browsed
udp        0      0 0.0.0.0:49902           0.0.0.0:*                           898/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                898/avahi-daemon: r
udp6       0      0 fe80::78bb:3175:6f6:123 :::*                                5339/ntpd
udp6       0      0 ::1:123                 :::*                                5339/ntpd
udp6       0      0 :::123                  :::*                                5339/ntpd
udp6       0      0 :::58476                :::*                                898/avahi-daemon: r

 

[Tuetchen]

well if the local connection works its obviously not a problem with the binding of ports. So yeah i would guess firewall/router/provider blocking things - but definetly not a sinusbot problem

 

[KILLERMANTV]

Sinusbot ports are allowed in firewall so problem is in sinusbot.

 

[Tuetchen]

Dude if you can access it locally it cant be a sinusbot problem end of story

 

[KILLERMANTV]

Then tell me why i can't access it through disabled firewall?

 

[Tuetchen]

router/provider blocking things

 

[KILLERMANTV]

Everything in lan is working except sinusbot.

 

[Tuetchen]

So again - are you trying to access it via your public address or via the LAN address?

 

[KILLERMANTV]

Via lan (192.168.0.157:8087)

 

[KILLERMANTV]

Hello?

 

[lingmaaki]

When connecting to a website, if Google Chrome browser fails to fetch the website to the browser, it throws an error saying "This site can't be reached Error" – ERR_CONNECTION_TIMED_OUT. It means the server is taking too much time to replying. The main reason behind this error is your computer can’t be able to access the internet connection or maybe something blocking your network to establishing a connection. Apart from the Network issue, there can be multiple reasons why this error shows up. Before going to any fix, please make sure the server you want to open is exist. If server exist, there are numerous solutions which can be used to solve this error.

Clear your Chrome browsing data
Check your Network Cables, Restart your Router and Reconnect
Check your Windows Host File
Remove Proxy
Flush DNS and reset TCP/IP
Run Chrome Cleanup Tool