search

airdcpp-web / airdcpp-webclient

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

WebUI not properly loading from time to time. Firefox-ESR #455

Closed slrslr closed 11 months ago

slrslr commented 1 year ago

Current UI and client versions:

Application version AirDC++w 2.12.1-8-gaa1d x86_64 Web UI version 2.12.0

Hello, it happen from time to time. UI does not properly load and log file does not show any error. Web browser Firefox ESR 102.12 shows something (screenshot is below).

Most recently updated log file 2023-07-system.log last lines:

[2023-07-04 14:30] File list refresh initiated for the path /path/here/
[2023-07-04 14:30] The directory /path/here/ has been refreshed (420.97 KiB of files have been added for hashing; they won't be visible in the file list until they have finished hashing)
[2023-07-04 14:30] The directory /path/here/subdir/ has finished hashing: 2 files (420.97 KiB) have been hashed in 0 second (58.73 MiB/s)
[2023-07-04 14:58] File list refresh initiated for the path /path/here/subdir/
[2023-07-04 14:58] The directory /path/here/subdir/ has been refreshed (3.02 MiB of files have been added for hashing; they won't be visible in the file list until they have finished hashing)
[2023-07-04 14:58] The directory /path/here/subdir/ has finished hashing: 5 files (3.02 MiB) have been hashed in 0 second (201.48 MiB/s)
[2023-07-04 15:04] File list refresh initiated for the path /path/here/subdir/subdir2/
[2023-07-04 15:04] The directory /path/here/subdir/subdir2/ has been refreshed (228.71 MiB of files have been added for hashing; they won't be visible in the file list until they have finished hashing)
[2023-07-04 15:04] The directory /path/here/subdir/subdir2/ has finished hashing: 118 files (228.71 MiB) have been hashed in 0 second (460.19 MiB/s)

If is needed full DCPlusPlus.xml or full particular log, please let me know how to share it in private.

Operating system:

Debian 11 with KDE (latest stable)

Steps to reproduce the issue:

Issue happens randomly not aware about how to reproduce it. But i think that it sometimes happen right on the start and is fixed by killing and restarting.

Screenshots

airdc-fail-webpage-nologentries

maksis commented 1 year ago

I see that you are using HTTPS that doesn't make much sense when accessing localhost. Will the issue happen with HTTP?

slrslr commented 1 year ago

I see that you are using HTTPS that doesn't make much sense when accessing localhost. Will the issue happen with HTTP?

I was unable to access via HTTP only - connection timeout if i remember correctly. Already killed it so can not verify again.

maksis commented 1 year ago

Already killed it so can not verify again.

What did you kill? The app or HTTP access?

slrslr commented 1 year ago

app (has no shutdown button)

maksis commented 1 year ago

There's a menu item for shutting down the application in the Application widget that is on the home page.

Do you mean that you are no longer able to do any testing with app?

slrslr commented 1 year ago

I see, the shutdown button is well hidden. I can test the app but not in dead state (when issue was filled). I have got all errors and log details. If it is not enough, you should tell me how to record better details exactly.

maksis commented 1 year ago

It's a network error in the browser based on your logs. I suspect that it has something to do with using HTTPS with a self signed cert. I recommend using HTTP instead of HTTPS.

slrslr commented 1 year ago

Thank you, I have switched to HTTP http://127.0.0.1:5600 (it has different port from HTTPS, which is confusing for a noob like me), i will update this in case issue repeats. Still you can not do anything so there is some user friendly message suggesting to use HTTP or a redirect to it or something in app log or on the WebUI that tells basic user what to try? If no ok. Maybe this can be close until/if issue reappear.

maksis commented 1 year ago

I could probably add a help message under web server settings discouraging people from using HTTPS unless they know what they are doing