Ticket: CORS Issue Blocking Signup on Local Installation
@mimo Just created a ticket
Question: Can't signup account on local installation
Attempted: Google Sign in: Access to fetch at 'https://postiz.homenet.lan/api/auth/oauth/GOOGLE' from origin 'http://localhost:5000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. Using Email: Access to fetch at 'https://postiz.homenet.lan/api/auth/register' from origin 'http://localhost:5000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Working On: Register account to try demo version
Using Postiz On: Docker compose
Take it from here @Postiz
Question: Can't signup account on local installation
Attempted: Google Sign in: Access to fetch at 'https://postiz.homenet.lan/api/auth/oauth/GOOGLE' from origin 'http://localhost:5000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. Using Email: Access to fetch at 'https://postiz.homenet.lan/api/auth/register' from origin 'http://localhost:5000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Working On: Register account to try demo version
Using Postiz On: Docker compose
Take it from here @Postiz
7 Replies
@Postiz please help @mimo
maybe try adding the ALLOWED_ORIGINS parameter in the base postiz service?
and also add the youtube ids for google integration btw
make sure roll the access keys kinda exposed urs here 😶🌫️
@Postiz please help @mimo
@Postiz please help @mimo
I have the same issue.
Just tried a fresh install on a fresh VM, Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://localhost:5000/api/auth/register. (Reason: CORS request did not succeed). Status code: (null).
try to install caddy and run from https://postiz.homenet.lan
https://www.alanbonnici.com/2024/12/howto-self-host-postiz-on-ubuntu-on.html
HowTo Self Host Postiz on Ubuntu (on Proxmox VE)
This blog is about security and computing related topics with occassional hobby activities thrown in.
That did not help. Your example.yml on the page is full of errors and even after fixing them it was still unable to 'docker compose up'.
I then used the default example .yml from postiz documentation and ran into the same error as before.