mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-11 17:48:44 -05:00
after I deploy, internel error happen #8
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Originally created by @rogerBridge on GitHub (Jul 9, 2021).
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 : )
@kolaente commented on GitHub (Jul 9, 2021):
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?
@rogerBridge commented on GitHub (Jul 9, 2021):
Vikunja api version v0.17.0+61-5b825f1cc8
Built with go1.16.5
I use docker, sir, docker-compose.yml from your website
Sir, could you tell me how to verify it? thank you : )
@kolaente commented on GitHub (Jul 9, 2021):
Does this work:
docker-compose exec db mysql -u <vikunja user> -p<vikunja password> vikunja? (substitute the values from the config)@rogerBridge commented on GitHub (Jul 9, 2021):
sir, I did it, and it shows a long text
@kolaente commented on GitHub (Jul 10, 2021):
Mhh that does not look like it should. Does this work:
docker-compose exec db mysql -u <vikunja user> -p vikunja- it should ask you for the db password you have in thedocker-compose.ymlfile.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?
@rogerBridge commented on GitHub (Jul 10, 2021):
yes, sir, I am sorry, I face some issue in my real life, I will give it to you
here is:
and I have a nginx-server in then same network: nginx-net, and I use nginx webserver as a reverse proxy to visit 'proxy'
@kolaente commented on GitHub (Jul 11, 2021):
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?
@rogerBridge commented on GitHub (Jul 11, 2021):
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
@rogerBridge commented on GitHub (Jul 12, 2021):
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 : (
@rogerBridge commented on GitHub (Jul 12, 2021):
maybe just config error in nginx-proxy-manager, but I check it complete, I don't find something is incorrect
@rogerBridge commented on GitHub (Jul 12, 2021):
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
@kolaente commented on GitHub (Jul 12, 2021):
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.