Ticket: Cannot Register/Login - Coolify Deployment Issues
@Smurffiction Just created a ticket
Question: Can't register or Login -
Attempted: - tested http://localhost:5000 iunstead of my domain (same issue) - tested with my domain https://social.censored.site:5000 - tried different composer files found on the Github and Discord I will attach files and Screenshots below in the thread
Working On: Coolify Deployment
Using Postiz On: Coolify
Take it from here @Postiz
Question: Can't register or Login -
Attempted: - tested http://localhost:5000 iunstead of my domain (same issue) - tested with my domain https://social.censored.site:5000 - tried different composer files found on the Github and Discord I will attach files and Screenshots below in the thread
Working On: Coolify Deployment
Using Postiz On: Coolify
Take it from here @Postiz
29 Replies
Tech stack:
Namecheap Domain
Ubuntu VPS from IONOS
resend
Coolify (latest version)
Postiz (latest version)
@Postiz please help @Smurffiction
@Postiz please help @Smurffiction
😦
Hey @Smurffiction I think you have the same issue as a lot of people around .
Using a subdomain that is not common , it’s getting unauthorized.
Only the subdomains in the GitHub file are authorized
https://github.com/gitroomhq/postiz-app/blob/main/libraries/helpers/src/subdomain/all.two.level.subdomain.ts
GitHub
postiz-app/libraries/helpers/src/subdomain/all.two.level.subdomain....
📨 The ultimate social media scheduling tool, with a bunch of AI 🤖 - gitroomhq/postiz-app
If you are going to use locally you can use something like postiz.homenet.lan
And this shall work for you
@m4rk so i need to buy a other domain (like .com.de) and cant use it on toplevel domain like censored.site?
You can open a PR to add the censored.site domains and that shall work but it might take a bit
censored will be my own domain. So you mean to PR to add ".site"? But its not an subdomain.
For example my domain is (fictional) postiz.site
I install it with Coolify, as domain i set https://postiz.site:5000
Also when keeping the from coolify given url with the http://postiz-xxx.ipadress.sslip.io:5000
i can connect to the Frontend, register a user, but when login it just loads endless.
Console shows the following on chrome:
uh to translate, he means that right now to make it easier, it would need to be like postiz.domain.com, NOT postiz.subdomain.domain.com. If the domain.com is NOT in the two-level listing, it won't make an exception.
I'd imagine it would be similar to being thought up as a two-level subdomain if it was something like .com.de like postiz.domain.com.de would technically count as domain being subdomain due to the tld address,
cause many were having issues like synology.me addresses weren't working (i.e. dock.name.synology.me)
Correct
Although the PR has been placed and approved for synology.me
We are just awaiting for it to bu pushed into prod 🙂
Is there a way I can track whether or not this has been pushed to prod?
I tried doing just xxxxx.synology.me instead of xxxx.xxxx.synology.me and still getting the 'Cookie "auth" ahs been rejected for invalid domain" error
Hi everyone, does this thread mean that Postiz cannot be used with xxxx.xxxx.duckdns.net ?
Correct. At least not until it is part of the updated allow list. I unfortunately do not know when it is unfortunately.
Has the Syno domain already been include in the updated allow list?
I don't know the answer to that myself as well. It is showing in the Github appearing as accepted, but I don't know if anyone is merging it.
I don't use Syno dns in many things, but I had to settle with changing mine anyways.
yes it has
also on your .env file remember to use this:
If you cannot use a certificate (HTTPS), add the following environment variable to your .env file:
NOT_SECURED=true
Weird. Syno domain doesn't work for me at all
What error are you getting ?
Is it still the infinite login ?
Yes that is what I'm seeing, infinite login screen. But error in console when doing so is for "Cookie auth has been rejected for invalid domain".
Check your ssl certificate in 99% sure you have an invalid one
If this is true , you will need to have and .env. And in there place the variable NOT_Secure=true
does your certificate looks something like this :
Would the synology domain not be considered secure as it has an SSL certificate issued by Let's Encrypt? Looks quite different from that one you sent
hmm you seem to have a valid one issued by lets encrypt
All synology domains would
That's the service they use
and what if.... you test using the env variable NOT_SECURED=true ( on the .env file)
I totally can, sorry. Was just confused why because it doesn't fit the use case
Unfortunately..... same issue
