You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already got it to work when accessing it directly. However I need to run it as a reverse proxy with nginx.
I followed this guide you published: https://github.com/butlerx/wetty/blob/main/docs/nginx.md.
Additionally I also have this line in my nginx config, however I dont really know if it has something to do with the error: add_header Access-Control-Allow-Origin *;
To Reproduce
Steps to reproduce the behavior:
Go to https://pfcloud.ddns.net:8080/wetty and you should get get same error.
You will also get notified that this is a dangerous site. This is I think a side effect of the error as this didn´t occur when I accessed it directly and not through the reverse proxy.
Open the console and you should see the exact same error and some others in the console.
Expected behavior
Well my expectation was that it would work exactly as it does when not routing it through a reverse proxy.
The text was updated successfully, but these errors were encountered:
I-dont-code-til-death
changed the title
Hello Guys,
Refused to display in a frame because it set 'X-Frame-Options' to 'deny'
Jun 10, 2023
Describe the bug
Hello guys,
I get the following error in the chrome console when trying to connect to wetty:
I already got it to work when accessing it directly. However I need to run it as a reverse proxy with nginx.
I followed this guide you published: https://github.com/butlerx/wetty/blob/main/docs/nginx.md.
Additionally I also have this line in my nginx config, however I dont really know if it has something to do with the error:
add_header Access-Control-Allow-Origin *;
To Reproduce
Steps to reproduce the behavior:
You will also get notified that this is a dangerous site. This is I think a side effect of the error as this didn´t occur when I accessed it directly and not through the reverse proxy.
Expected behavior
Well my expectation was that it would work exactly as it does when not routing it through a reverse proxy.
The text was updated successfully, but these errors were encountered: