Error 404 page not found after update to 1.9.0 #615

Closed
opened 2025-11-13 12:05:47 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @TehMaat on GitHub (Aug 25, 2025).

Tell me what you need to help me. Logs are useless

Originally created by @TehMaat on GitHub (Aug 25, 2025). Tell me what you need to help me. Logs are useless
Author
Owner

@jtenniswood commented on GitHub (Aug 25, 2025):

I'm getting the same thing, not sure if it was my setup.

@jtenniswood commented on GitHub (Aug 25, 2025): I'm getting the same thing, not sure if it was my setup.
Author
Owner

@oschwartz10612 commented on GitHub (Aug 26, 2025):

Hum this has come up a couple of times. Looking into it...

Do you see a site defined on the targets? We migrated the targets in
this release.

@oschwartz10612 commented on GitHub (Aug 26, 2025): Hum this has come up a couple of times. Looking into it... Do you see a site defined on the targets? We migrated the targets in this release.
Author
Owner

@TehMaat commented on GitHub (Aug 26, 2025):

I don't how I fixed it but I did.

I changed integration port on the config to the new port (3004) and disabled socket docker in the site configuration

@TehMaat commented on GitHub (Aug 26, 2025): I don't how I fixed it but I did. I changed integration port on the config to the new port (3004) and disabled socket docker in the site configuration
Author
Owner

@jtenniswood commented on GitHub (Aug 26, 2025):

Same. After nuking and resetting this up with 1.8, I then did a backup and updated to 1.9.1 without issue.

@jtenniswood commented on GitHub (Aug 26, 2025): Same. After nuking and resetting this up with 1.8, I then did a backup and updated to 1.9.1 without issue.
Author
Owner

@Esa-mimbias commented on GitHub (Aug 27, 2025):

May sound like an "IT Crowd" answer, but have you tried to log off and on again your session ?

juste encountered this behavior:

  • restarted the containers
  • returned to the WebUI, every link returns a 404
  • log off and on my session
  • every link works fine.

Perhaps a timed auto logout feature on the webUI + periodic check if session is still valid - and logout if not, may be a related feature ?

@Esa-mimbias commented on GitHub (Aug 27, 2025): May sound like an "IT Crowd" answer, but _have you tried to log off and on again_ your session ? juste encountered this behavior: - restarted the containers - returned to the WebUI, every link returns a 404 - log off and on my session - every link works fine. Perhaps a timed auto logout feature on the webUI + periodic check if session is still valid - and logout if not, may be a related feature ?
Author
Owner

@oschwartz10612 commented on GitHub (Aug 27, 2025):

We also identified an issue on Discord with someone who had 2 exit nodes
registered. This has been a long standing bug and I am going to fix in
next patch shortly. I think you can fix by editing the db and removing
all the nodes and restarting hopefully. OR check the wireguard key in
the config dir and delete the other node. You will have to convert it to
a wg pub key. Let me know if anyone tries this.

sudo apt install sqlite3

sqlite3 config/db/db.sqlite

sqlite> SELECT * FROM "exitNodes";

1|Exit Node
zBdMiSzt|100.89.128.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil
2|Exit Node
/XODtRJ8|100.89.129.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil

DELETE FROM exitNodes;

@oschwartz10612 commented on GitHub (Aug 27, 2025): We also identified an issue on Discord with someone who had 2 exit nodes registered. This has been a long standing bug and I am going to fix in next patch shortly. I think you can fix by editing the db and removing all the nodes and restarting hopefully. OR check the wireguard key in the config dir and delete the other node. You will have to convert it to a wg pub key. Let me know if anyone tries this. sudo apt install sqlite3 sqlite3 config/db/db.sqlite sqlite> SELECT * FROM "exitNodes"; 1|Exit Node zBdMiSzt|100.89.128.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil 2|Exit Node /XODtRJ8|100.89.129.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil DELETE FROM exitNodes;
Author
Owner

@Soitora commented on GitHub (Aug 27, 2025):

sudo apt install sqlite3

sqlite3 config/db/db.sqlite

sqlite> SELECT * FROM "exitNodes";

1|Exit Node
zBdMiSzt|100.89.128.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil
2|Exit Node
/XODtRJ8|100.89.129.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil

sqlite> DELETE FROM exitNodes;

This fixed it for me!

On Unraid the permissions were a bit tricky. Since apt isn’t available in the Unraid console, I instead used WSL2 on my Windows machine and accessed the database file over SAMBA. To avoid permission errors when running DELETE FROM, I temporarily changed the file owner to my SAMBA user account. After making the change, I switched ownership back to nobody.

@Soitora commented on GitHub (Aug 27, 2025): > sudo apt install sqlite3 > > sqlite3 config/db/db.sqlite > > sqlite> SELECT * FROM "exitNodes"; > > 1|Exit Node > zBdMiSzt|100.89.128.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil > 2|Exit Node > /XODtRJ8|100.89.129.1/24|[REDACTED]|51822|http://gerbil:3003||0||gerbil > > sqlite> DELETE FROM exitNodes; This fixed it for me! On Unraid the permissions were a bit tricky. Since `apt` isn’t available in the Unraid console, I instead used WSL2 on my Windows machine and accessed the database file over SAMBA. To avoid permission errors when running `DELETE FROM`, I temporarily changed the file owner to my SAMBA user account. After making the change, I switched ownership back to `nobody`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#615