[bug]: Plane won't display on the public URL when rebooting its container

[Sedation6612]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

My technical setup is on this ticket: #7042
I have a feeling the two might be in relation to each other, but, I am using Nginx Proxy Manager on a separate container.

When I create a plane instance, everything works swell, but as soon as I restart the container that Plane is hosted in, I can no longer connect to Plane via the public URL, and I get the generic "Connection reset" errors from chrome.

However, when I navigate to the internal hostname that I have set for the container, it does load a blank page and the plane tab information (icon & name).

The ONLY way I'm able to fix this is by running prime-cli repair, and then everything will work as intended, but on every container restart, I need to run that command.

I'm not entirely sure what to provide, I'd be happy to provide whatever I can, thanks!

Steps to reproduce

Install a instance of Plane on a container
After it's successfully installed, navigate to the site it's hosted at
Then restart the container

Upon refreshing the page you were previously at, you'll get a connection reset generic error.

This also happens when you configure the plane instance via god-mode with various settings, so the initial setup doesn't prevent this from happening.

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

vv1.9.2