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
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
I'm trying to run paperless on macOS 10.15.5 Catalina on Docker. Had it working fine once but ran into consumption problems so I reinstalled.
Now, I've tried for some time to get the new containers up and running but get stuck with following docker error log message when I docker-compose up -d :
ERRORS: ?: (corsheaders.E013) Origin 'localhost:8080' in CORS_ORIGIN_WHITELIST is missing scheme or netloc HINT: Add a scheme (e.g. https://) or netloc (e.g. example.com).
I've checked the settings.py and docker-compose.yml files but it's all correctly schemed with http (also tried https), since there were multiple google entries stating that that might be the issue. I changed the ports in the settings file from 8080 to 8000 with no luck. To figure out if it's a docker problem, I ran a test container but with no problems, it was running fine. Has anybody run into the same error message and can tip me into the right direction? Thx
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to run paperless on macOS 10.15.5 Catalina on Docker. Had it working fine once but ran into consumption problems so I reinstalled.
Now, I've tried for some time to get the new containers up and running but get stuck with following docker error log message when I
docker-compose up -d
:ERRORS: ?: (corsheaders.E013) Origin 'localhost:8080' in CORS_ORIGIN_WHITELIST is missing scheme or netloc HINT: Add a scheme (e.g. https://) or netloc (e.g. example.com).
I've checked the settings.py and docker-compose.yml files but it's all correctly schemed with http (also tried https), since there were multiple google entries stating that that might be the issue. I changed the ports in the settings file from 8080 to 8000 with no luck. To figure out if it's a docker problem, I ran a test container but with no problems, it was running fine. Has anybody run into the same error message and can tip me into the right direction? Thx
The text was updated successfully, but these errors were encountered: