-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
after I deploy, internel error happen #2
Comments
Which vikunja version is that? How are you hosting it (docker etc)? The error message looks like the db credentials are incorrect. Can you verify the ones you have in the Vikunja config file are correct? |
Vikunja api version v0.17.0+61-5b825f1cc8
I use docker, sir, docker-compose.yml from your website
Sir, could you tell me how to verify it? thank you : ) |
Does this work: |
sir, I did it, and it shows a long text
|
Mhh that does not look like it should. Does this work: I can see though you're using mysql 8 which isn't explicitly supported and thus might have issues. Could you share your compose file? |
yes, sir, I am sorry, I face some issue in my real life, I will give it to you
and I have a nginx-server in then same network: nginx-net, and I use nginx webserver as a reverse proxy to visit 'proxy' |
Does this work: docker-compose exec db mysql -u root -psupersecret vikunja` or do you get the mentioned help text output? The compose file looks correct to me. The error you originally got looks like the mysql container went down at some point but I'm not sure why that might be the case. Anything in the logs? |
sir, I try the command: "docker-compose exec db mysql -u root -psupersecret vikunja" and nothing output, I think this is my problem, when I try caddy as a reverse proxy, vikunja works fine, when I try use nginx as a reverse proxy, vikunja works bad, I think something is wrong in my /etc/nginx/conf.d, , I will figure out it and explain it to you, please keep this issue open, thank you sir |
sir, I think maybe the permission issue is because I use nginx-proxy-manager, I try just use nginx and put nginx docker and vikunja docker-compose into the same network, it works fine, when I use nginx-proxy-manager and vikunja docker-compose into same network, it works bad, I think maybe some bug in nginx-proxy-manager, but I don't know why, these is not vikunja's issue, sorry : ( |
maybe just config error in nginx-proxy-manager, but I check it complete, I don't find something is incorrect |
I thougth I found why, because I add some container, network-alias is "db", and vikunja's docker-compose has a container name db, so, vikunja-api don't know which db should it dial, haha, I am too stupid, sir |
That's interesting it does that. I though docker-compose would "know" what alias would be valid in what network and make sure there aren't any duplicates. Glad you figured it out! As this appears to be solved, I'm closing this issue. Feel free to ping me if you have other questions. |
Pin dependencies Reviewed-on: https://kolaente.dev/vikunja/desktop/pulls/2 Co-Authored-By: renovate <renovatebot@kolaente.de> Co-Committed-By: renovate <renovatebot@kolaente.de>
hello sir,
I am a fans of your vikunja, I face some issue recently, when I try do some http request, vikunja_api respond: "internel error", I try to find the cause, here is log:
it just show that access denied, but I don't know why, could you help me to fix it? thank you sir : )
The text was updated successfully, but these errors were encountered: