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

SSL corruption for loading frontend #143

Open
Stronkness opened this issue Dec 9, 2022 · 8 comments
Open

SSL corruption for loading frontend #143

Stronkness opened this issue Dec 9, 2022 · 8 comments

Comments

@Stronkness
Copy link

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
eiffelvis_no_ssl

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.
eiffelvis_ssl

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

@AeroStun
Copy link
Member

AeroStun commented Dec 9, 2022

Just to make sure, have you tried this on a browser with the cache flushed, ideally in anonymous browsing?
The issue sounds like a client-side caching behavior.

@Stronkness
Copy link
Author

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:

Uncaught (in promise) DOMException: The operation is insecure. [bundle.js:2]

@AeroStun
Copy link
Member

AeroStun commented Dec 9, 2022

@AeroStun
Copy link
Member

AeroStun commented Dec 9, 2022

I guess you didn't because our documentation does not mention the need to do that when doing non-manual deployment.
I will update the documentation to clarify. (#144)

@Stronkness
Copy link
Author

Stronkness commented Dec 9, 2022

I did a hard refresh in the browser and the new layout appeared with SSL enabled. And yes, I did build with EIFFELVIS_SSL = true. Do I also need to change anything in the Dockerfile?

Now this appears, not sure if this is due to a problem on my side or something is not compatible.
Mixed Content: The page at 'https://eiffelvisURL' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://eiffelvisURL/ws'. This request has been blocked; this endpoint must be available over WSS.

Uncaught (in promise) DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

@AeroStun
Copy link
Member

AeroStun commented Dec 9, 2022

Just to clarify, you changed EIFFELVIS_SSL in the Dockerfile, not in the frontend/.env, correct?

@Stronkness
Copy link
Author

I changed it in both of them. first i .env file and then in Dockerfile, now both are True

@RuthgerD
Copy link
Collaborator

Need to find some time to setup up ssl locally to test things out, unsure when though

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