Skip to content
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

post deployment with latest version, website is blank #2658

Open
Rajeshwaric7 opened this issue Jan 16, 2025 · 3 comments
Open

post deployment with latest version, website is blank #2658

Rajeshwaric7 opened this issue Jan 16, 2025 · 3 comments

Comments

@Rajeshwaric7
Copy link

I am testing the latest version of 11.17 using simple docker containers. however, page looks empty as below.

One observation is index.html file used be under website/public folder however it has got changed due to migration to Vite.

image

i am not able to login to docker container might be gcr.io/distroless/base does not include any shell or debugging tools.
docker logs:

docker logs 56116ab3b4f9
{"level":"info","ts":1737026641.7846947,"caller":"yopass-server/main.go:68","msg":"Starting yopass server","address":":1337"}
{"level":"info","ts":1737026654.6618295,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026654.6604054,"method":"GET","uri":"/","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026654.9361944,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026654.9360297,"method":"GET","uri":"/assets/index-majqvoMx.js","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026654.9362273,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026654.9360566,"method":"GET","uri":"/assets/index-B9OZSai_.css","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026655.248238,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026655.248119,"method":"GET","uri":"/favicon.png","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026655.5426924,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026655.5425894,"method":"GET","uri":"/favicon.ico","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026657.4693775,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026657.4692411,"method":"GET","uri":"/","protocol":"HTTP/1.1","responseStatus":304,"responseSize":0}
{"level":"info","ts":1737026672.0888388,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026672.088326,"method":"GET","uri":"/","protocol":"HTTP/1.1","responseStatus":200,"responseSize":1240}
{"level":"info","ts":1737026672.4460142,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026672.445676,"method":"GET","uri":"/assets/index-B9OZSai_.css","protocol":"HTTP/1.1","responseStatus":200,"responseSize":23585}
{"level":"info","ts":1737026672.4467466,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026672.4456937,"method":"GET","uri":"/assets/index-majqvoMx.js","protocol":"HTTP/1.1","responseStatus":200,"responseSize":982890}
{"level":"info","ts":1737026675.6755364,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026675.6751308,"method":"GET","uri":"/favicon.png","protocol":"HTTP/1.1","responseStatus":200,"responseSize":14516}
{"level":"info","ts":1737026676.034013,"caller":"server/logging.go:42","msg":"Request handled","host":"172.17.0.1","timestamp":1737026676.03338,"method":"GET","uri":"/favicon.ico","protocol":"HTTP/1.1","responseStatus":200,"responseSize":15086}

@YBFree19
Copy link

i have its problem too

@Rajeshwaric7
Copy link
Author

Team, Any update on this?

@WalterPinkman
Copy link

I encountered the white screen today in Edge and Chrome (no issues with Firefox), but I'm not sure it has anything to do with the latest version. In the browser console there was an some error message about Web Crypto API. A couple of Ctrl+F5 (refresh, ignoring cache) seem to have fixed it though. Give this a try.

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

3 participants