Skip to content

Blank page on upgrade (1.7.8 to 1.9.x) #462

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

Open
boomam opened this issue Apr 1, 2025 · 7 comments
Open

Blank page on upgrade (1.7.8 to 1.9.x) #462

boomam opened this issue Apr 1, 2025 · 7 comments

Comments

@boomam
Copy link

boomam commented Apr 1, 2025

Hi,
I have just upgraded Docuseal from v1.7.8 to v1.9.7.
Upon upgrade, the webserver no longer displays through the reverse proxy in use.

Health checks on the paths of / & /up also fail.

Rolling back to v1.7.8 fixes accessibility, but i am no longer able to upload files.

Were there some breaking changes between 1.7.8 & above?

Thanks.

@omohokcoj
Copy link
Contributor

@boomam could your please provide docker error log?

@boomam
Copy link
Author

boomam commented Apr 1, 2025

This is all that is in the log -

Puma starting in single mode...
* Puma version: 6.5.0 ("Sky's Version")
* Ruby version: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux-musl]
*  Min threads: 15
*  Max threads: 15
*  Environment: production
*          PID: 1
WARNING: Nokogiri was built against libxml version 2.13.6, but has dynamically loaded 2.13.4

@omohokcoj
Copy link
Contributor

@boomam the log doesn't contain errors but the next line is missing:

@boomam
Copy link
Author

boomam commented Apr 1, 2025

Not possible, its running through an ingress controller in k8s, that translates it to 443 w/ TLS.

Are there any other log locations, in the container itself?

@boomam
Copy link
Author

boomam commented Apr 2, 2025

@omohokcoj - i did a little more testing.
Reverting the database to a backup that i took before the upgrade from 1.7.8, and restarting a 1.9.5 image, to ensure that nothing could possibly interrupt any db scheme upgrades - same issue as above.

Reverting again, and setting the image back to 1.7.8, GUI works again - same upload issue though.

Any suggestions?

@omohokcoj
Copy link
Contributor

@boomam the app didn't contain any complex/long migrations between those two versions.
Try to update to 1.7.9 to see if it works - there might be an issue with k8s update process you use.

@boomam
Copy link
Author

boomam commented Apr 2, 2025

Hi,
I had already tried 1.8.0 previously, which works fine.
I also tested via a separate, non-k8s install, pointed at the same database, same issue.
It is not a k8s issue - k8s 'update process' is the exact same as docker or podman's, as in, a new image gets pulled, and the container (pod) gets restarted with that image in place of the original.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants