-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error code 404 received #36
Comments
Which API version are you using? |
That is probably the problem. This app doesn't yet support the update that changed namespaces to lists. |
Oh. How can I fix it? Or do I have to wait for an update to the app? |
You should wait for the update. @kolaente can tell you if downgrading is an option but I don't think it is. I'm working on it, it'll probably be one to two more weeks as I'm on holiday right now :). Sorry for the inconvenience. |
Okay, I'll wait. Thanks for your help |
You could restore from the backup you did before upgrading and then downgrade to 0.20 to wait until the app can work with the new version. Downgrading isn't really supported and won't work most of the time. |
Uh well there's a problem with that idea. I didn't backup the previous version. I am running Vikunja in a docker container and I have a watchtower container that updates all the containers to the latest version. So... I cannot restore from backup |
Can't I just change the image that is used without data loss? |
Release 0.1.1-beta fixes this, it now supports projects. |
great! |
So everything was working fine, but now when I open the app, I get "Error code 404 received" and when I click the popup, it says something about the API not working. Vikunja works perfectly when I'm using the Web version.
I should note that I am using Nginx Proxy Manager to Proxy Vikunja to a sub-domain. But I am proxying the API port to /api/v1. This is happening to all the devices I have this app installed. I am using the 0.1.0-beta release
The text was updated successfully, but these errors were encountered: