tkohhh

joined 1 year ago
[–] tkohhh@waveform.social 1 points 1 year ago

This makes sense, and I do have a dollar sign in my password...

However, I have confirmed that postgres does in fact parse the password correctly, as I can log in with the defined username/password combo directly using psql

So I think that disproves this theory, doesn't it?

[–] tkohhh@waveform.social 1 points 1 year ago* (last edited 1 year ago)

Thank you for enlightening me on the -W option in psql. I have successfully logged in using the expected password for lemmy. This points to something with the connection string. According to the error log, the connection string being used is:

postgres://lemmy:<my percent-encoded password>@postgres:5432/lemmy

As far as I can tell, the percent encoding is correct. Any ideas how to troubleshoot this further?

edit: it just occurred to me that my container name is lemmy_postgres_1, not postgres as was entered in my lemmy.hjson file. Let's see if changing that will work...

edit2: no, that had no effect. I'm getting the authentication error for user lemmy on both the lemmy container and the postgres container. :(

[–] tkohhh@waveform.social 1 points 1 year ago* (last edited 1 year ago)

Frustratingly, when you use psql on the terminal, it does not prompt you for a password. So I'm still not sure if the password works or not :(

Ahh, ok... if you add the -W option when logging in to psql (psql -U lemmy -W), it will prompt for the password.

The password works! So, apparently it's something with the connection string.

[–] tkohhh@waveform.social 0 points 1 year ago (2 children)

Username definitely matches!

And yes, I have several special characters, but the password is surrounded by single quotes in docker-compose.yml, so that should not matter, right?

 

I'm trying to get Lemmy up and running on an Ubuntu 22.04 host. I've followed this guide supplemented by googling.

I can actually get to the front end, but it gives me "There was an error on the server." When I dig into the logs, I see this:

"thread 'main' panicked at 'Error connecting to postgres://lemmy:<my pg password>@postgres:5432/lemmy: FATAL:  password authentication failed for user \"lemmy\"\n","stream":"stderr","time":"2023-06-26T03:14:17.47460915Z"}

The only thing I can find about this error related to Lemmy is this thread, which indicates that the password was not defined in the docker-compose.yml file prior to starting the containers. I have since redone the configuration three times, each time deleting the volumes folder and double-checking that my postgre password is correct both in docker-compose.yml and lemmy.hjson.

Any ideas what might be the problem? Thank you kindly for any help you can provide!

[–] tkohhh@waveform.social 1 points 1 year ago

I got it going... the main problem was that the ports for the proxy container were defined in a confusing way. Rather, the port definition should be symmetrical (e.g. 1236:1236) and not conflated with the lemmy server port (8536). Then, the nginx_internal.conf should be set to listen on 1236 only.

[–] tkohhh@waveform.social 0 points 1 year ago* (last edited 1 year ago) (1 children)

Do you mind sharing what exactly you changed in order to get it to work? I got nginx_internal.conf installed, but did not make any changes to it. I'm not able to get the UI using http://:1236

I'm not a complete newb when it comes to nginx, but I'm having a hard time understanding what all the different parts are here. For instance, what is the lemmy-ui container for? Is that what needs to be exposed for me to access the UI? If so, I don't see any port mapping the in container definition, so is it hard-coded to use a specific port?

Any help you can provide is greatly appreciated!

[–] tkohhh@waveform.social 1 points 1 year ago

Influxdb + grafana for me! Good stuff!

[–] tkohhh@waveform.social 1 points 1 year ago

I don't know for sure... but my instinct is that NAT reflection is moot in that case, because your connection is going out past the edge router and doing the DNS query there, which will then direct you back to your public IP. I'm sure there's somebody around that knows the answer for certain!

[–] tkohhh@waveform.social 3 points 1 year ago (3 children)

If your router has NAT reflection, then the problem you describe is non existent. I use the same domain/protocol both inside and outside my network.

[–] tkohhh@waveform.social 3 points 1 year ago* (last edited 1 year ago)

I like Photostructure as a way to browse my photos. It does logical deduping, and automatic organization of your photos (if you want it to). Like some others mentioned in this thread, it's a very young software, but the developer is very active and transparent about the progress.

Edit to add link: photostructure.com

[–] tkohhh@waveform.social 1 points 1 year ago (1 children)

Tangential point: if your "smart home" can be shut down by a third party, then you aren't Smart Homing correctly.

view more: next ›