-
Notifications
You must be signed in to change notification settings - Fork 3
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
SSL corruption for loading frontend #143
Comments
Just to make sure, have you tried this on a browser with the cache flushed, ideally in anonymous browsing? |
In incognito mode the new layout appears as the first image. But no nodes are showing. Same with a different browser i've never tested this before. However it gives an error in console:
|
Did you build the frontend with |
I guess you didn't because our documentation does not mention the need to do that when doing non-manual deployment. |
I did a hard refresh in the browser and the new layout appeared with SSL enabled. And yes, I did build with Now this appears, not sure if this is due to a problem on my side or something is not compatible.
|
Just to clarify, you changed |
I changed it in both of them. first i .env file and then in Dockerfile, now both are True |
Need to find some time to setup up ssl locally to test things out, unsure when though |
This error is strange. When using your latest deployment without SSL it works like a charm with latest features and fast performance. This is what it looks like
However, when applying SSL to the project it appears to go back to a previous version somehow and bugs out. The tool is very slow, doesn't scroll properly and nodes freeze on screen when trying to zoom in and out. You can't move around with the mouse and no arrows appear connecting the nodes.
Are there issues with SSL for this project? Do I need to apply something special or enable something to make this work? I have valid certificates and eiffelvis is hosted at https if im using SSL. I also changed the nginx conf file a bit to properly work with SSL. This has worked previously in #102 but failed when we upgraded to the latest version #141
The text was updated successfully, but these errors were encountered: