Hello everyone, I need some help please.
Summary
I shared link of my App with someone and the person told me that only sees a blank page with streamlit when opening with Chrome on MacOS. I guess there must be something this person can do to solve it like clearing cache or trying a different browser (will try later on today when gets home).
I tried all the browsers on browserstack.com and works fine for me. I canāt see anything we are doing wrong.
Expected behavior:
Streamlit authenticator widget, sidebar with 3 pages (including home).
Actual behavior:
Blank page (Chrome MacOS)
Thanks a lot in advance!
1 Like
Hi @Neteresy,
Thanks for posting! Is this the URL (https://msimsi.streamlit.app/) of your app?
If yes, the app is running with no issues.
As youāve stated, the user likely needs to log out of their Streamlit Community Cloud account, clear browser cookies, and then log back in and open the app.
Let me know if this resolves the issue.
1 Like
@Neteresy Today it happened for my app as well. Kindly reboot the application for temporary fix.
@community, Kindly do the permanent fix. In Logs, its got stuck after updated an app.
1 Like
Oh, I forgot to put the link. Good thing you got it from the picture. I deployed it on AWS EC2 now:
www.psypy.com
Do you think this will help prevent that error?
Thanks very much!
Hi @Neteresy,
The link you provided is not working.
Hi @Neteresy,
www.psypy.com is not working. showing DNS error. After Deployed, did you checked whether it was working?.
Your Streamlit app is working as seen below, but the AWS deployment link above is not.
Hello, the issue was that AWS DNS was still propagating since activated the routing with AWS Route 53 to two different servers. And because I didnĀ“t flush the DNS I was still being able to access and didnĀ“t realize. I believe that now itĀ“s working as expected.
Would you be so kind to double check please?
And do you think being hosted in the deployed instances would less likely present the original āblank pageā problem?
Thanks again!
Hey, thank you for answering!
tonykip reported the same problem with my link, so I quote the message I just sent to him.
Hello, the issue was that AWS DNS was still propagating since activated the routing with AWS Route 53 to two different servers. And because I didnĀ“t flush the DNS I was still being able to access and didnĀ“t realize. I believe that now itĀ“s working as expected.
Would you be so kind to double check please?
And do you think being hosted in the deployed instances would less likely present the original āblank pageā problem?
Thanks again!
