SOLVED Needed help with gitea setup - web unavailable + how 2 setup directories

dAlexis

Dabbler
Joined
Aug 15, 2015
Messages
41
Installing gitea from available apps TrueNAS-SCALE-22.12.4.2 (btw, complete noob in git, but cannot even attach 2 web portal).
Two questions:

How 2 setup correct root URL? was setting http://192.168.x.x:30008/gitea - no connection or entering TrueNAS login screen. BTW, may I set another IP 4 the pod?

Maybe the problem is in directory permissions
For making backup easier I created 4 directories, made chown 2 apps (please, see below)
Postgres made chown during install, but other dirs untouched - should I chown them 2 docker? DB iwas running, according 2 the log, btw
Waiting 4 advice

BTW, app was active during 1-2 min, but now is in deploing 1/2 state again...

vivaldi_HxINnABziE.png


admin@truenas[/mnt/RAIDZ2/...../gitea]$ ls -la
total 37
drwxr-xr-x 6 apps apps 6 Jan 22 13:26 .
drwxr-xr-x 6 root root 6 Jan 22 13:22 ..
drwxr-xr-x 2 apps apps 2 Jan 22 13:26 backup
drwxr-xr-x 2 apps apps 2 Jan 22 13:26 config
drwxr-xr-x 2 apps apps 2 Jan 22 13:26 data
drwx------ 19 999 docker 25 Jan 23 12:29 database
 
Last edited:

dAlexis

Dabbler
Joined
Aug 15, 2015
Messages
41
Partially solved, after watching default install data I repeated directory structure with permissions below

drwx------ 2 1000 1000 3 Jan 24 10:02 config
drwxr-xr-x 15 1000 1000 15 Jan 24 10:07 data
drwxr-xr-x 2 root root 2 Jan 24 10:01 pgBackup
drwx------ 19 999 docker 26 Jan 24 10:01 pgData

r-x on data was set by me 2 watch config

Now web UI is shown (I set only IP:port w/o /gitea postfix) howevew postges does not want 2 start, if placed not in ix directory.

listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
....
2024-01-24 09:37:45.479544+00:002024-01-24 09:37:45.479 UTC [108] FATAL: password authentication failed for user "gitea"

So cannot guess default password. How happens, that it cannot run from different place? I don't want to have data on SSD apps pool, especially database. Advice needed...
BTW, how it managed 2 work differently - only db path changed....
 
Last edited:

dAlexis

Dabbler
Joined
Aug 15, 2015
Messages
41
Was needed to re-enter all the directories and clean them manualy - works now. Seems, that reinstalling with default paramerers normally overrides previous DB password, but not changing with customized path
 

brandon_

Cadet
Joined
Jan 28, 2024
Messages
5
Was needed to re-enter all the directories and clean them manualy - works now. Seems, that reinstalling with default paramerers normally overrides previous DB password, but not changing with customized path
I'm having the same/similar issue. Would you mind saying more about what you did to resolve the issue?
 

dAlexis

Dabbler
Joined
Aug 15, 2015
Messages
41
I'm having the same/similar issue. Would you mind saying more about what you did to resolve the issue?
1. Create the directory structure by mv\chmod\chown, exactly as in post #2
2. If it's already done, but no success - uninstall with removing docker image (maybe, not needed, in case)
3. Before next install do chmods 2 enter all directories mentioned and clean all in them.
4. Map the directories accordingly during fresh install

IMHO - Postges and other directories cleanup is performed only with default settings.
 
Top