Cloudflare hosting domain

[thecivvie]

Trying to use Cloudflare to host the subdomain for the docker server but it keeps saying the domain does not match any trusted origins. It is added as the plain domain name and https://domain name and still no joy. I can access the car using the ip of the Pi but the car will not be able to.

I know I am missing a trick

[developerfromjokela]

Hi.

Are you exposing OpenCARWINGS server directly to cloudflare from its http port, or is it behind nginx/apache?

[thecivvie]

Directly to Cloudflare. Say I use http(s)://carwings.domain and add that clouflare, I have a tunnel going to http://192.168.1.9:8015 (I mapped 8015 to 80). I get an error message saying to add carvings.domain to the whitelist but I added it

in carwings/settings.py

I have:

SECURITY WARNING: don't run with debug turned on in production!

DEBUG = True

ALLOWED_HOSTS = ['carwings.domain','192.168.1.9']

[thecivvie]

OK, this is the error screen:

Forbidden (403)
CSRF verification failed. Request aborted.
Help
Reason given for failure:
Origin checking failed - https://opencar.DOMAIN does not match any trusted origins.

In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django’s CSRF mechanism has not been used correctly. For POST forms, you need to ensure:
Your browser is accepting cookies.
The view function passes a request to the template’s render method.
In the template, there is a {% csrf_token %} template tag inside each POST form that targets an internal URL.
If you are not using CsrfViewMiddleware, then you must use csrf_protect on any views that use the csrf_token template tag, as well as those that accept the POST data.
The form has a valid CSRF token. After logging in in another browser tab or hitting the back button after a login, you may need to reload the page with the form, because the token is rotated after a login.
You’re seeing the help section of this page because you have DEBUG = True in your Django settings file. Change that to False, and only the initial error message will be displayed.
You can customize this page using the CSRF_FAILURE_VIEW setting.

[developerfromjokela]

OK, this is the error screen:

Forbidden (403)
CSRF verification failed. Request aborted.
Help
Reason given for failure:
Origin checking failed - https://opencar.DOMAIN does not match any trusted origins.

In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django’s CSRF mechanism has not been used correctly. For POST forms, you need to ensure:
Your browser is accepting cookies.
The view function passes a request to the template’s render method.
In the template, there is a {% csrf_token %} template tag inside each POST form that targets an internal URL.
If you are not using CsrfViewMiddleware, then you must use csrf_protect on any views that use the csrf_token template tag, as well as those that accept the POST data.
The form has a valid CSRF token. After logging in in another browser tab or hitting the back button after a login, you may need to reload the page with the form, because the token is rotated after a login.
You’re seeing the help section of this page because you have DEBUG = True in your Django settings file. Change that to False, and only the initial error message will be displayed.
You can customize this page using the CSRF_FAILURE_VIEW setting.

Try adding this to your config:

CSRF_TRUSTED_ORIGINS = [
'https://opencar.DOMAIN'
]

[thecivvie]

That did it :) Not sure I will use it, but want to play :)