Skip to content
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

Incorrect PostgreSQL Connection String When Using Unix Sockets with port #28864

Closed
sdvcrx opened this issue Jan 20, 2024 · 1 comment · Fixed by #28865
Closed

Incorrect PostgreSQL Connection String When Using Unix Sockets with port #28864

sdvcrx opened this issue Jan 20, 2024 · 1 comment · Fixed by #28865
Labels

Comments

@sdvcrx
Copy link
Contributor

sdvcrx commented Jan 20, 2024

Description

Hi! I want connect PostgreSQL DB via unix socket.

Based on documentation and #24552 (comment) , I have configured HOST as follows:

DB_TYPE = postgres
HOST = /var/run/postgresql:6432

However, I'm encountering an error during the ORM engine initialization. The error log is as follows:

routers/common/db.go:23:InitDBEngine() [I] Beginning ORM engine initialization.
routers/common/db.go:30:InitDBEngine() [I] ORM engine initialization attempt #1/10...
cmd/web.go:194:serveInstalled() [I] PING DATABASE postgres
routers/common/db.go:36:InitDBEngine() [E] ORM engine initialization attempt #1/10 failed. Error: dial unix /var/run/postgresql:6432/.s.PGSQL.6432: connect: no such file or directory

Gitea Version

1.21.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

command-line

Database

PostgreSQL

Copy link

github-actions bot commented Mar 1, 2024

Automatically locked because of our CONTRIBUTING guidelines

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant