Apicurio/apicurio-studio

Apicurio Studio page loader spinning for-ever after login

sandeepsuvit opened this issue ยท 9 comments

Hi Team,

From today after i login to the application the application page just shows the loader page and isn't loading the application. Any thoughts around this? This happened multiple times for me.

image

Screenshot of the console

image

Hi @sandeepsuvit

This will be corrected with the PR #2132 ๐Ÿ‘

I've been getting the same problem for a couple of days now. Same messages in the browser developer console as well.

Same problem for me. I not able to use the online version (https://studio.apicur.io/) for a few days now because of this issue due to CORS errors (as seen in my dev console). Just tested again with v0.2.61.Final and got the same result

@clabonte and @andapony is it still not working or is the CORS problem solved? I cannot reproduce the problem either on studio.apicur.io.

If you're still getting the problem, could you let me know what browser you are using?

Also maybe try clearing your browser cache and reloading.

It's been working fine for me over the last several days. Thanks!

Working for me as well! Thanks for the excellent work on this great solution!

@EricWittmann I'm hosting ApiCurio Studio in AWS, and upgraded to 0.2.61.Final as suggested here to resolve the max frame size issue in 0.2.59, however now I receive a 403 error for all static resources.
image

No other configuration changes have been made (using the same environment variables as in 0.2.59.Final).

I also tried configuring the CORS_ALLOWED_ORIGINS environment variable in hopes that it would fix the issue, but no success.

What is most odd is that logs do not display anything regarding these failed requests and the UI works in Firefox.

Chrome and Edge are both broken, though.

Hi @berlinger-ciprianpetrisor - you likely need to set the QUARKUS_HTTP_CORS_ORIGINS environment variable to * in both the -api and also the -ui pods. I don't know why it works in Firefox but not in Chrome, but we discovered the same thing and that was the fix.

In future releases this will not be necessary, but it is for 61.

@EricWittmann
Thank you very much, that seems to have fixed the problem!