We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm trying to host the Stremio server Docker image on an AWS EC2 instance. For example, the server's IP is:
https://aws-server-ip:12470/
and I've set NO-CORS=1 to disable the server's CORS.
i need help to solve the following issue:
When accessing https://aws-server-ip:12470/ and using the server's embedded web application, it works fine; I can watch any movies.
When using the Stremio website and setting the streaming server to https://aws-server-ip:12470/, it also works fine.
But when I try to use this Stremio web interface, setting the same streaming server to https://aws-server-ip:12470/, it shows a CORS error:
[How it looks in the Stremio web interface]
[How it looks when debugging the browser]
The text was updated successfully, but these errors were encountered:
@FelipeOtz it is NO_CORS not NO-CORS
NO_CORS
NO-CORS
Sorry, something went wrong.
No branches or pull requests
I'm trying to host the Stremio server Docker image on an AWS EC2 instance. For example, the server's IP is:
https://aws-server-ip:12470/
and I've set NO-CORS=1 to disable the server's CORS.
i need help to solve the following issue:
When accessing https://aws-server-ip:12470/ and using the server's embedded web application, it works fine; I can watch any movies.
When using the Stremio website and setting the streaming server to https://aws-server-ip:12470/, it also works fine.
But when I try to use this Stremio web interface, setting the same streaming server to https://aws-server-ip:12470/, it shows a CORS error:
[How it looks in the Stremio web interface]
[How it looks when debugging the browser]
The text was updated successfully, but these errors were encountered: