docuseal icon indicating copy to clipboard operation
docuseal copied to clipboard

Blank page on upgrade (1.7.8 to 1.9.x)

Open boomam opened this issue 1 year ago • 7 comments

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.

boomam avatar Apr 01 '25 22:04 boomam

@boomam could your please provide docker error log?

omohokcoj avatar Apr 01 '25 22:04 omohokcoj

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

boomam avatar Apr 01 '25 22:04 boomam

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

  • Listening on http://0.0.0.0:3000 Maybe the port is already occupied by some other process

omohokcoj avatar Apr 01 '25 22:04 omohokcoj

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 avatar Apr 01 '25 22:04 boomam

@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?

boomam avatar Apr 02 '25 00:04 boomam

@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.

omohokcoj avatar Apr 02 '25 10:04 omohokcoj

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.

boomam avatar Apr 02 '25 12:04 boomam