-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank webpage #401
Comments
Hi,
|
Don't waste too much time on this, it's probably wildly random and not an actual bug with the tool 😅
Everything is marked as INFO, repetition of the same periodic tasks, except this single WARNING here:
Not sure why the self-hosted version would be asking about an internet connection, but that machine has full internet access.
|
There is certainly something wrong with the sysreptor-app container (as the connection is reset). |
I have both performed restarts and fully torn down and rebuilt all the containers one by one apart from the database mutliple times to no avail. I ran the update script as well. Whatever the issue is, it seems only a fresh install, possibly in a fresh VM too, will fix it, I just wanted to try to salvage the database. I'm sorry I couldn't help you pinpoint what went wrong. Edit: I can indeed confirm that a fresh setup works perfectly with nothing out of the ordinary. |
I can offer you a temporary Professional license, so you can try to backup your existing installation and to restore the backup on a new server. |
So I may just be wasting your time here and it's an issue purely on my side (in which case just close the issue), but you told me on Discord to open an issue here. I tried to look into things and see what info I can give you.
The web page is currently still blank for me, tried different browsers just in case, tried visiting the page in my VM as well.
Edge returns a 502.
I tried rebuilding the containers (apart from the database), that did not help. Today I ran the update script to see what happens, but the issue persists.
The only errors I can find in the Docker logs are coming from the caddy container.
I can't figure out why the connection is being reset. Nothing has changed in my setup to help me explain it.
The text was updated successfully, but these errors were encountered: