Replies: 4 comments 4 replies
-
Hi @ddtjco , thanks for your feedback. There are many reasons for this, I need some details. "custom url" means you deployed the streamlit app on your server? If so |
Beta Was this translation helpful? Give feedback.
-
Thanks for following up. Turns out we had an error with our url rewrite rules that was causing the issues. Once we fixed those, it began to work. |
Beta Was this translation helpful? Give feedback.
-
I have solved the problem |
Beta Was this translation helpful? Give feedback.
-
If I deployed Streamlit in Kubernetes and used an Nginx ingress for reverse proxy, how should I approach this issue? |
Beta Was this translation helpful? Give feedback.
-
I recently enabled pygwalker on a streamlit application. We are hosting the streamlit application locally on a Windows server using a custom url. If I hit the streamlit application from the localhost url, everything with pygwalker works as expected. But I access the application using our custom url, the pygwalker screen stays stuck on the "Loading Graphic-Walker UI" screen. I notice in the inspector tools that the resource (_stcore/_pygwalker/comm/...) returns a 404 error when accessing from our url, but not from the localhost.
Beta Was this translation helpful? Give feedback.
All reactions