Login TypeError
@chribonn Just created a ticket
Question: I access postiz via localhost:5000. When I tried to register with Google nothing happens when I click. When I try to use the form below I get the error below Error: General error: TypeError: NetworkError when attempting to fetch resouces. Please check your browser console
Attempted: I restarted, tried to log in from another browser (Firefox and Chrome).
Working On: Ubuntu 24.04.1
Take it from here @Mod 🔥
Question: I access postiz via localhost:5000. When I tried to register with Google nothing happens when I click. When I try to use the form below I get the error below Error: General error: TypeError: NetworkError when attempting to fetch resouces. Please check your browser console
Attempted: I restarted, tried to log in from another browser (Firefox and Chrome).
Working On: Ubuntu 24.04.1
Take it from here @Mod 🔥
26 Replies
Can you check where the backend is running?
GitHub
[AB-0002]: google auth configuration simplified by OleksandrKuchere...
What kind of change does this PR introduce?
Google Auth and Google Youtube - are divided into two different environmental variables
Why was this change needed?
Login/SignIn/SignUp - should have ...
for auth/login should be configured clientId/accessKey/etc for google.
And the initial design of the system expects youtube/google - as one entity setup
Both the front and backend are running on localhost. I buit the solution based upon the following script: https://docs.postiz.com/installation/docker-compose#example-docker-composeyml-file. I replaced all references to postiz.your-server.com woth localhost
Want to clarify that both the Google as well as direct subscription form fail. Attaching a gif of what I experience.
@Mod 🔥 please help @chribonn
Heya @chribonn , the most likely cause of this is probably the NEXT_PUBLIC_BACKEND_URL is not set, and it's
undefined, causing the TypeError.
Thanks for the video by the way, that really helps.
Could you check your environment variables for the NEXT_PUBLIC_BACKEND_URL, and also check your web developer logs?
Normally you press F12 to open the Web Developer consoleI confirm that NEXT_PUBLIC_BACKUP_URL does not exist
Thanks
Hija @xcons, you wouldn't happen to have an update. I am recording a tutorial on how to install Postiz and am blocked.
Thanks 📝
Thanks 📝
Hello, probably i have the same issue.
Sounds like what i had also
I am writing a tutorial, I have the the entire process recorded and noted. If this is a blocking point than maybe I can take a break from this topic. I had in mind something along these lines: https://www.alanbonnici.com/2024/08/proxmox-nut-homelab-howto-step-0.html This is a multipart series comprising article and video on Proxmox.
Proxmox-NUT Homelab HOWTO : Step 0 : The Proxmox-NUT HomeLab HowTo:...
This blog is about security and computing related topics with occassional hobby activities thrown in.
@heps @Brotherperson You wrote that you had it. How did you solve it?
I did not. Someone tolled me is is because it gets directed to http not https
Thanks, I was under the impression that localhost could be run at http. Can someone please explain whether this is correct? If not I have to go back and revisit the topic
My reasoning was to keep the first version of the HowTo at a minimum, adding caddy at a later stage.
That's what the docs say 🙂
hey all
localhost can run as http, yep
@chribonn , do you have "https" in your env URLS? I think so, change them to just "http" for localhost
@chribonn ping?
yes I do
I'll try it out.
Same error. I included what I observe and the Console output. Could the Cross Domain form be the issue?
I am attaching the docker-compose.yml file in case you want to reproduce it.
I used the example code at https://docs.postiz.com/installation/docker-compose#example-docker-composeyml-file and did the following:
- replaced all https://postiz.your-server.com with http://localhost
- populated the string JWT_SECRET
As it says on the wiki, you have to use https to login
You'll be not able to do it with http
localhost is fine
As the error message says, please open your browser console
(F12 on most systems)
That will tell you the "real" error message - Postiz doesn't have access to that
I was asled to try http. My original report was when I was using https
In the animated gif I did that reproduced below
I beleive I shared this information when I originally raised the issue 🤔
@chribonn it's because you have two different URLs
one with :5000 for the FRONTEND_URL
and NEXT_PUBLIC_BACKEND_URL does not have :5000 in it