search

airdcpp-web / airdcpp-webclient

Communal peer-to-peer file sharing application for file servers/NAS devices
https://airdcpp-web.github.io
175 stars 32 forks source link

Connection timed out #344

Closed Flwk closed 4 years ago

Flwk commented 4 years ago

Current UI and client versions:

AirDC++w 2.6.1 I use Chrome 80.0.3987.132

Operating system:

The server i use is on Debian 9 64 bits

Steps to reproduce the issue:

So, it've been a long time i use the web client of AirDc, but when i reboot my server, and try to launch like usual, i have timed out error. The port is open, and i don't have any error on the server side.

Do you know how can i debug this issue ?

Sorry for my english, it's not my native language

Cordialy

maksis commented 4 years ago

Did you check the help message at the bottom of "Settings" -> "Connectivity"? There are two links that might be helpful. I'd also recommend using the latest application version.

Flwk commented 4 years ago

Did you check the help message at the bottom of "Settings" -> "Connectivity"? There are two links that might be helpful. I'd also recommend using the latest application version.

I use it on a debian server, so i can only use the command line :'(

maksis commented 4 years ago

Where do you get that timeout error...? When opening the Web UI in browser?

Flwk commented 4 years ago

Where do you get that timeout error...? When opening the Web UI in browser?

Yes

maksis commented 4 years ago

Ah I thought that you meant file transfers.

Is the UI accessible from the server where the app is running? You can try wget http://localhost:5600 (or whichever port you are using) from the command line (it should produce error 404).

Flwk commented 4 years ago

Ah I thought that you meant file transfers.

Is the UI accessible from the server where the app is running? You can try wget http://localhost:5600 (or whichever port you are using) from the command line (it should produce error 404).

--2020-03-25 17:49:22--  http://localhost:5600/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:5600... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-03-25 17:49:22 ERROR 404: Not Found.

I have this, but when i try to connect the Ui whit Chrome, i have a connection timed-out error

maksis commented 4 years ago

How have you validated that the port is open? Have you used a port checker, such as https://www.yougetsignal.com/tools/open-ports/ ? Did you try the latest application version?

Flwk commented 4 years ago

How have you validated that the port is open? Have you used a port checker, such as https://www.yougetsignal.com/tools/open-ports/ ? Did you try the latest application version?

Yeah, i'v tried with this port checker, and it tell me that the port is open.

I don't know how to update AirDC++w with line command, i'valway did it with the Web Interface.

maksis commented 4 years ago

I don't know how to update AirDC++w with line command, i'valway did it with the Web Interface.

You can just replace the files and restart the application (it's not something that you can do from the Web UI).

You could also locate the config file WebServer.xml and see if there's is anything that could affect the connectivity (such as bind address)

Flwk commented 4 years ago

I'v found some Logs, and i still don't know where is the problem : 

[2020-03-25 17:48] Connectivity (IPv4 & IPv6): Determining the best connectivity settings...
[2020-03-25 17:48] Connectivity (IPv4): Public IP address detected, selecting active mode with direct connection
[2020-03-25 17:48] Connectivity (IPv6): IPv6 connectivity has been disabled as no public IPv6 address was detected
[2020-03-25 17:48] Updating GeoIP database...
[2020-03-25 17:48] GeoIP database could not be updated
[2020-03-25 17:48] File list refresh initiated

I've done the update, and i'm now on AirDC++w 2.7.0, and i have the same problem

maksis commented 4 years ago

Did you check the config file content? Based on your local wget test, the application seems to be available locally. If you can't access it remotely and there is no unusual config in WebServer.xml, can't think of anything in the application itself that could cause it. Of course you can try it without the old config files too, just to be sure.

Flwk commented 4 years ago

Did you check the config file content? Based on your local wget test, the application seems to be available locally. If you can't access it remotely and there is no unusual config in WebServer.xml, can't think of anything in the application itself that could cause it. Of course you can try it without the old config files too, just to be sure.

I'v try with new filw config files, and i can't access it. Do you know if it can be IPTables problem ? Or maybe Nginx ?

maksis commented 4 years ago

Are you using it with nginx..? Yes, it can be the problem then. Nginx, iptables, anything is possible. It's difficult to say without knowing your system/network config.

maksis commented 4 years ago

Were you able to solve it?

Flwk commented 4 years ago

no it's not working

Le ven. 8 mai 2020 à 14:27, maksis notifications@github.com a écrit :

Were you able to solve it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/airdcpp-web/airdcpp-webclient/issues/344#issuecomment-625791415, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYYMYKDXZG5SKAKULXCRELRQP3CRANCNFSM4LG3KFOQ .

maksis commented 4 years ago

I'm going to close the issue as there is no indication that issue is caused by AirDC++. I'd recommend trying to load the Web UI without nginx/iptables/other services that might prevent the access (maybe such services also have information in their own logs about the problem).