Hi Glenn, On Tue, Jul 7, 2020 at 10:44 PM Glenn Hamblin <ghamblin@gmail.com> wrote:

Hi, I'm an extreme noob with LedgerSMB and Docker and Postgres so please go gentle on me :-)

No problem and welcome to our list! :-)

I have setup LedgerSMB on docker on my Linux machine. And I know I connected to it when I first set it up. But when I tried to access it today I only get a connection refused message from the browser.

Ok. Have you restarted your machine since you created the container? If so, you might need to start the container again: containers are created without the option to start on boot by default.

The containers are running and they are supposedly running on port 5762 however, when I run ss -plnt I do not see anything on that port. I must have done something wrong, but I don't know what. Does anyone here have any suggestions?

Hmm. I never tried to find out about port bindings from containers before today, actually :-) I tried what you did and didn't see the port binding from root either (using lsof). However, my container *is* running and I accessed it just before I ran the command. However, when I run `docker exec -ti ldmaster_lsmb_1 ss -ilnp` (ldmaster_lsmb_1 is my container name), I *do* see the application waiting for connections. I'm not sure what Docker does to achieve that. Maybe you can application bound to the port too when you run that command? Also, maybe the application is available not through localhost, but through the container's IP address? You can find out the IP address of the container through the command `docker inspect ldmaster_lsmb_1`. I usually find the IP address in the last 25 lines of the output. I access my containers through http://172.23.0.5:5762/ (because I have many containers with all versions of LedgerSMB since 1.4 running at the same time, I can't have them all bound to localhost). Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.