Fetch error Unexpected token is not valid JSON #49

Closed
opened 2025-12-29 14:23:22 +01:00 by adam · 5 comments
Owner

Originally created by @Lifailon on GitHub (Mar 29, 2025).

Continuation of the problem after #73 in the new release 0.10.0. Authorization does not work, immediately lets you into the interface and an error occurs (on the screenshot).

Image

Procedure:

~/godoxy > /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/yusing/godoxy/main/scripts/setup.sh)"
Using curl for downloads
Setting up GoDoxy
Branch: main
Creating directory "config"
Do you want to overwrite ".env"? (y/n): y
Downloading ".env.example" to ".env"
Done
Europe/Moscow
Downloading "compose.example.yml" to "compose.yml"
Done
Downloading "config.example.yml" to "config/config.yml"
Done
Setting up login user
Enter login username: admin
Enter login password: admin
Setting up login user "admin" with password "admin"
Setting up autocert for SSL certificate
Do you want to enable autocert? (y/n): n
Setup finished
~/godoxy > docker-compose up -d
[+] Running 2/2
 ✔ Container godoxy           Started                                                                                                                                                                                                                                                                                  2.3s
 ✔ Container godoxy-frontend  Started 
Originally created by @Lifailon on GitHub (Mar 29, 2025). Continuation of the problem after #73 in the new release 0.10.0. Authorization does not work, immediately lets you into the interface and an error occurs (on the screenshot). ![Image](https://github.com/user-attachments/assets/6ebe1e53-0af8-4400-bbad-4c6ab4db712a) Procedure: ```shell ~/godoxy > /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/yusing/godoxy/main/scripts/setup.sh)" Using curl for downloads Setting up GoDoxy Branch: main Creating directory "config" Do you want to overwrite ".env"? (y/n): y Downloading ".env.example" to ".env" Done Europe/Moscow Downloading "compose.example.yml" to "compose.yml" Done Downloading "config.example.yml" to "config/config.yml" Done Setting up login user Enter login username: admin Enter login password: admin Setting up login user "admin" with password "admin" Setting up autocert for SSL certificate Do you want to enable autocert? (y/n): n Setup finished ~/godoxy > docker-compose up -d [+] Running 2/2 ✔ Container godoxy Started 2.3s ✔ Container godoxy-frontend Started ```
adam closed this issue 2025-12-29 14:23:22 +01:00
Author
Owner

@yusing commented on GitHub (Mar 29, 2025):

From the screenshot, it was somehow fetching from your nginx proxy manager instead of the GoDoxy API. Make sure you do not have port conflict (by default GoDoxy uses port 80, 443 (with autocert), 8888 for API, 3000 for WebUI) and make sure that GoDoxy is started successfully (check docker compose logs).

@yusing commented on GitHub (Mar 29, 2025): From the screenshot, it was somehow fetching from your nginx proxy manager instead of the GoDoxy API. Make sure you do not have port conflict (by default GoDoxy uses port 80, 443 (with autocert), 8888 for API, 3000 for WebUI) and make sure that GoDoxy is started successfully (check `docker compose logs`).
Author
Owner

@Lifailon commented on GitHub (Mar 29, 2025):

@yusing yes! I did have NPM running (web interface on port 8888), but I disabled it (deleted the container), after clearing the cache it helped. BUT, the authorization problem persists, I still can't log in to the interface...

Image

@Lifailon commented on GitHub (Mar 29, 2025): @yusing yes! I did have NPM running (web interface on port 8888), but I disabled it (deleted the container), after clearing the cache it helped. BUT, the authorization problem persists, I still can't log in to the interface... ![Image](https://github.com/user-attachments/assets/ecfef0ea-093e-43eb-a007-e16b53f6b7eb)
Author
Owner

@yusing commented on GitHub (Mar 29, 2025):

https://github.com/yusing/godoxy/issues/73#issuecomment-2763019055

If you desire not to use https, or just testing out GoDoxy, you can set GODOXY_API_JWT_SECURE to false to disable the "secure" flag in cookies.

Also it won't work if you access it with IP:Port rather than a url with hostname http://sub.domain.tld.

@yusing commented on GitHub (Mar 29, 2025): https://github.com/yusing/godoxy/issues/73#issuecomment-2763019055 If you desire not to use https, or just testing out GoDoxy, you can set GODOXY_API_JWT_SECURE to false to disable the "secure" flag in cookies. Also it won't work if you access it with IP:Port rather than a url with hostname http://sub.domain.tld.
Author
Owner

@Lifailon commented on GitHub (Mar 29, 2025):

Added a variable for the backend (proxy), it worked, thanks! The tool is very functional, everything works!

In my opinion, it would be useful to add this information to the README to speed up the launch process. Most people (like me, since I can try a dozen tools in a day for comparison or study) would like to quickly launch and check the functionality.

@Lifailon commented on GitHub (Mar 29, 2025): Added a variable for the backend (proxy), it worked, thanks! The tool is very functional, everything works! In my opinion, it would be useful to add this information to the README to speed up the launch process. Most people (like me, since I can try a dozen tools in a day for comparison or study) would like to quickly launch and check the functionality.
Author
Owner

@yusing commented on GitHub (Mar 29, 2025):

Will add this to README soon. Thanks.

@yusing commented on GitHub (Mar 29, 2025): Will add this to README soon. Thanks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#49