Vikunja Setup - Connection Refused
RodTGG opened this issue · 17 comments
Truenas Scale - Dragonfish
Pretty sure the issue is the URL parameter
Have tried the following
- Server.IP:Port - Connection Refused
- localhost:Port - Parameter not a valid URI
- vikunja.ix-vikunja.svc.cluster.local:Port - Parameter not a valid URI
Anybody know what the URL is supposed to be?
Hello,
Have you checked the tooltip?
I did, the first thing i tried was the server ip + the app port
they looked like examples
i dont want to use a domain or hostname just the ip allocated to truenas + the port
Then use the first example and replace the ip and port?
Thats the first thing i did
what i wrote above are the things i tried without the values replaced
Did you include http:// ?
not including it would not result in an invalid URI by parameter validator
I've just tried a new install with
http://192.168.1.100:31002 and worked fine.
If this does not work for you (replacing ip and port where needed)
Share the container logs and the configuration
will grab logs in a second,
im using http://192.168.50.4:30050
and web port: 30050
do they need to be different? does it have to be port 31002?
They should match. I take that this ip is your truenas ip right?
yep
cant see anything special in the logs
2024-08-22 22:43:56.774109+10:00�[38;5;6mredis �[38;5;5m22:43:56.77 �[0m
2024-08-22 22:43:56.775674+10:00�[38;5;6mredis �[38;5;5m22:43:56.77 �[0m�[1mWelcome to the Bitnami redis container�[0m
2024-08-22 22:43:56.777191+10:00�[38;5;6mredis �[38;5;5m22:43:56.77 �[0mSubscribe to project updates by watching �[1mhttps://github.com/bitnami/containers�[0m
2024-08-22 22:43:56.778807+10:00�[38;5;6mredis �[38;5;5m22:43:56.77 �[0mSubmit issues and feature requests at �[1mhttps://github.com/bitnami/containers/issues�[0m
2024-08-22 22:43:56.780369+10:00�[38;5;6mredis �[38;5;5m22:43:56.77 �[0m
2024-08-22 22:43:56.781975+10:00�[38;5;6mredis �[38;5;5m22:43:56.78 �[0m�[38;5;2mINFO �[0m ==> ** Starting Redis setup **
2024-08-22 22:43:56.801798+10:00�[38;5;6mredis �[38;5;5m22:43:56.80 �[0m�[38;5;2mINFO �[0m ==> Initializing Redis
2024-08-22 22:43:56.817394+10:00�[38;5;6mredis �[38;5;5m22:43:56.81 �[0m�[38;5;2mINFO �[0m ==> Setting Redis config file
2024-08-22 22:43:56.872104+10:00�[38;5;6mredis �[38;5;5m22:43:56.87 �[0m�[38;5;2mINFO �[0m ==> ** Redis setup finished! **
2024-08-22 22:43:56.872133+10:002024-08-22T22:43:56.872133115+10:00
2024-08-22 22:43:56.888907+10:00�[38;5;6mredis �[38;5;5m22:43:56.88 �[0m�[38;5;2mINFO �[0m ==> ** Starting Redis **
2024-08-22 22:43:56.899447+10:001:C 22 Aug 2024 22:43:56.899 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-08-22 22:43:56.899482+10:001:C 22 Aug 2024 22:43:56.899 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
2024-08-22 22:43:56.899512+10:001:C 22 Aug 2024 22:43:56.899 # Configuration loaded
2024-08-22 22:43:56.899875+10:001:M 22 Aug 2024 22:43:56.899 * monotonic clock: POSIX clock_gettime
2024-08-22 22:43:56.900694+10:001:M 22 Aug 2024 22:43:56.900 * Running mode=standalone, port=6379.
2024-08-22 22:43:56.900712+10:001:M 22 Aug 2024 22:43:56.900 # Server initialized
2024-08-22 22:43:56.902552+10:001:M 22 Aug 2024 22:43:56.902 * Creating AOF base file appendonly.aof.1.base.rdb on server start
2024-08-22 22:43:56.903160+10:001:M 22 Aug 2024 22:43:56.903 * Creating AOF incr file appendonly.aof.1.incr.aof on server start
2024-08-22 22:43:56.903190+10:001:M 22 Aug 2024 22:43:56.903 * Ready to accept connections
have just done a fresh install and still not working with http://192.168.50.4:31002
This seems to the redis container. Check the vikunja container. Sometimes ui will load the wrong container.
yep sorry, i didnt look at the drop down
2024-08-22 23:58:16.887143+10:002024-08-22T23:58:16.886973674+10:00: INFO ▶ config/InitConfig 001�[0m No config file found, using default or config from environment variables.
2024-08-22 23:58:16.890519+10:002024-08-22T23:58:16.890355841+10:00: INFO ▶ migration/Migrate 003�[0m Running migrations…
2024-08-22 23:58:16.954277+10:002024-08-22T23:58:16.954026465+10:00: INFO ▶ migration/Migrate 06a�[0m Ran all migrations successfully.
2024-08-22 23:58:16.954369+10:002024-08-22T23:58:16.954134937+10:00: INFO ▶ models/RegisterReminderCron 06b�[0m Mailer is disabled, not sending reminders per mail
2024-08-22 23:58:16.954431+10:002024-08-22T23:58:16.954182616+10:00: INFO ▶ models/RegisterOverdueReminderCron 06c�[0m Mailer is disabled, not sending overdue per mail
2024-08-22 23:58:16.954603+10:002024-08-22T23:58:16.9544939+10:00: INFO ▶ cmd/func27 06d�[0m Vikunja version v0.24.2
2024-08-22 23:58:16.957044+10:00⇨ http server started on [::]:30050
2024-08-22 23:58:29.214665+10:002024-08-22T23:58:29.214487664+10:00: WEB ▶ 172.16.0.1 GET 200 /health 24.342µs - kube-probe/1.26
2024-08-22 23:58:29.217047+10:002024-08-22T23:58:29.216977873+10:00: WEB ▶ 172.16.0.1 GET 200 /health 76.798µs - kube-probe/1.26
2024-08-22 23:58:39.213949+10:002024-08-22T23:58:39.213794575+10:00: WEB ▶ 172.16.0.1 GET 200 /health 41.67µs - kube-probe/1.26
2024-08-22 23:58:39.214083+10:002024-08-22T23:58:39.213919244+10:00: WEB ▶ 172.16.0.1 GET 200 /health 52.875µs - kube-probe/1.26
2024-08-22 23:58:49.213531+10:002024-08-22T23:58:49.213359132+10:00: WEB ▶ 172.16.0.1 GET 200 /health 42.716µs - kube-probe/1.26
2024-08-22 23:58:49.213636+10:002024-08-22T23:58:49.213430484+10:00: WEB ▶ 172.16.0.1 GET 200 /health 43.589µs - kube-probe/1.26
What's the output of
sudo k3s kubectl get svc -n ix-vikunjaAnd this
midclt call chart.release.get_instance "vikunja" | jq '.config'Run those on the truenas shell.