Redis password cannot have certain special characters. #690

New Issue

2024-07-23T12:31:51Z

4erf commented

2024-07-23 12:31:51 +00:00

(Migrated from gitea.com)

Could be useful to note in the README that the redis password cannot contain spcecial characters that will make the connection string invalid.

Struggled with this issue for +2 hours, the error given by the gitea pod was:

2024/07/23 09:54:18 routers/init.go:64:mustInit() [F] code.gitea.io/gitea/modules/cache.Init failed: dial tcp 127.0.0.1:6379: connect: connection refused

which is not very helpful.

I tried everything, until I noticed the issue was the password in the connection string containing special characters.

Could be useful to note in the README that the redis password cannot contain spcecial characters that will make the connection string invalid. Struggled with this issue for +2 hours, the error given by the gitea pod was: ``` 2024/07/23 09:54:18 routers/init.go:64:mustInit() [F] code.gitea.io/gitea/modules/cache.Init failed: dial tcp 127.0.0.1:6379: connect: connection refused ``` which is not very helpful. I tried everything, until I noticed the issue was the password in the connection string containing special characters.

😕 1

pat-s commented

2024-07-23 13:26:33 +00:00

(Migrated from gitea.com)

PRs welcome - although we can't do much here as we're only using the bitnami subchart. But worth a note!

justusbunsi commented

2024-07-23 17:52:01 +00:00

(Migrated from gitea.com)

If you can connect to Redis with your defined password by using a redis compatible interface (e.g. Redis Desktop Manager or similar) it means the Bitnami Chart properly handled your password and the issue is on our side while building the connection string. If you cannot connect to Redis at all, Bitnami has an issue as well.

@4erf Could you check and let us know? Maybe we only have to urlencode the password component of the url.

If you can connect to Redis with your defined password by using a redis compatible interface (e.g. Redis Desktop Manager or similar) it means the Bitnami Chart properly handled your password and the issue is on our side while building the connection string. If you cannot connect to Redis at all, Bitnami has an issue as well. @4erf Could you check and let us know? Maybe we only have to urlencode the password component of the url.

SpaceAceMonkey commented

2024-08-15 23:48:39 +00:00

(Migrated from gitea.com)

I also had this problem. I can connect to the Redis pod using redis-cli while the Gitea pod is in CrashLoopBackOff complaining about not being to connect to Redis. I don't have access to any other clients at the moment.

Sticking to letters and numbers in the password makes the deployment work.

I also had this problem. I can connect to the Redis pod using `redis-cli` while the Gitea pod is in CrashLoopBackOff complaining about not being to connect to Redis. I don't have access to any other clients at the moment. Sticking to letters and numbers in the password makes the deployment work.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lunny/helm-chart#690