Network-Error after Update #1725
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1725
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I just updated my app and frontend.
Now suddenly I get an network error when I open Vikunja.
The Browser log says its a request block (Cross-Origin).
I hava Vikunja installed in a docker and using the nginx-conf as you suggested.
Did I miss any changes in prefs or something like that (because I made no changes - I just downloaded the new available docker containers).
Actually Vikunja worked for me.
Do you have the api on a seperate port or host than the frontend? Cors errors should not occur if you have frontend and api on the same host.
Did you do any changes to the cors settings in the api?
Thanks for your fast reply.
Yes, I have them on seperate ports.
Therefore I have this nginx-settings:
server {
listen 8090;
}
Actually this worked. I didn't make any changes.
But after I updated the api and the frontend I get this network error.
I found out that the request is to http://localhost:3456/api/v1/info
But actually it should be http://192.168.2.30:3456/api/v1/info
I didnt write localhost anywhere...
Do you have an idea where this "localhost" is defined?
Again: Actually I didnt change anything.
Thanks for ur help.
EDIT: I recreated vikunja from the old docker-images (end of April) => there is no network-error.
So it seems there are some changes in the last update which produce this network-error...
Ah I see, did you build the frontend yourself or did you use the pre-built one?
I used the pre-built one (I just pulled from docker vikunja:latest)
The new version is capable of setting the api url (for cases where you have the api on a different server/port than the frontend) - it should however set it by default to
/api/v1on the same server.http://localhost:3456/api/v1is the default for that but it should be replaced at runtime.Could you show the generated html served by the frontend? The
window.API_URLpart is the interesting thing here.But if you're hosting with docker and are using the nginx example proxy configuration from the docs, you should be able to access the frontend at
/of your server and the api at/api/v1on the same server, without any ports.This is the generated html:
I tried to use the api-environment-variable.
Since now I didnt figured out how to use it correctly.
I set $VIKUNJA_API_URL to http://192.168.2.30:3456 (for my case).
Furthermore I dont need my personal nginx.conf (see above) anymore.
Did I get it right?!
Anyway with seetings I got the same html-output and window.API_URL = 'http://localhost:3456/api/v1' again.
Hmmm that's interesting, because try is running the same docker image and it works...
What frontend version are you using? You can see that on the js browser console when accessing the frontend (You need to enable
infooutput).This 0.13+2-d7b4b2189a is my frotend-version. It seems its the same like your try-version.
I the setting $VIKUNJA_API_URL to http://192.168.2.30:3456 correct in my case?
Or is it 192.168.2.30:3456 or http://192.168.2.30:3456/api/v1 or...?
You'd need to set it to the url where you can reach the api from your browser. If that's
http://192.168.2.30:3456/api/v1, you'd need to put that in. In general you can verify by accessing the info endpoint from a browser, say if your api is installed athttp://192.168.2.30:3456you should be able to accesshttp://192.168.2.30:3456/api/v1/infoand then would need to puthttp://192.168.2.30:3456/api/v1/inVIKUNJA_API_URL.I guess you're using the docker container as is without modifying anything?
yes correctly. I only mapped the port in the docker-container (8083 -> 80)
BTW: I can reach the api at http://192.168.2.30:3456/api/v1 , but when I use this as setting for $VIKUNJA_API_URL it still does not work.
Do u have any further ideas? It is possible that there is the bug and the ENV VIKUNJA_API_URL does not work correctly?
My wife is killing me... and want to change to this microsoft-service now :-(
I guess it does not replace the api url in the served index html? Can you try with curl (that bypasses any caching or service workers)
At this point I'd think it is possible... You can check that though:
docker exec <vikunja frontend container name> -it bash)cat /usr/share/nginx/html/index.htmlwindow.API_URL = '/api/v1'I tried it with curl and with "cat /usr/share/nginx/html/index.html"
Both of them shows window.API_URL = 'http://localhost:3456/api/v1' :-(
Honestly, I'm a bit lost here. It does not make any sense at all.
The whole point of docker containers is they are reproducable...
Have you tried throwing the container you had before away and starting a complete new one? No volumes or anything like that?
What do you get when running
sed -i "s/http\:\/\/localhost\:3456\/api\/v1/http\:\/\/192\.168\.2\.30\:3456\/api\/v1/g" /usr/share/nginx/html/index.htmlin the container and thencat /usr/share/nginx/html/index.html?That's the command that should be run on start which replaces the api url with the one from the env variable, just manually...
Does it work if you try to build the container manually? (just plain,
git clonethe repo and rundocker build .)?Do you get your api url if you clone the repo, change the api url in
public/index.htmland then build the docker container?Hey,
first I tried "sed -i "s/http://localhost:3456/api/v1/http://192.168.2.30:3456/api/v1/g" /usr/share/nginx/html/index.html" and this really already worked. The API_URL was 192.168.2.30 !
Great.
After this I tried ur second suggestion: I totally deleted the image, downloaded again and built it: And the environemt variable "VIKUNJA_API_URL" worked !!! So this did the trick.
After this I changed the VIKUNJA_API_URL again (for testing), but I couldnt change it. I had to remove everthing again and build it again to change the VIKUNJA_API_URL again.
Thats wired... Maybe its something with my Docker, because Im using Docker with a Synology NAS.
But anyway: Now Vikunja is working !!!!
Yeah.
Thanks for ur fast replies and help !!!!
Glad it works now!
Did you build the docker image as is or did you change the url and built after that?
That could be it, but I'm not sure why it is causing that. Maybe the synology docker runtime sets some volumes. Are you able to check that? Maybe even with
docker inspectfrom the cli?I didnt change anything. I just built it from the docker image.
I tried to check it from the cli but I cant get any further informations about how the Docker-App of Synology handle this.
Its weird but I ll keep it in mind that I have to think about it before changing any env in my containers ;-)
I guess NASes do weired stuff sometimes :)
Closing this as it seems to be resolved, feel free to reopen or create a new issue here or in the forum.