It works here. I can only guess why it doesn't work there:

• You have another program listening on localhost:8080 but not 192.168.1.10:8080, so Fossil binds to one but not the other.

• Your local firewall allows connections to one IP but not the other.

• You've got too many VMs/SSH sessions running, confusing you about which IP belongs to the machine Fossil is actually running on.

Any chance you once started a fossil ui and it is still running?

And that it was started during some testing in a directory that has since been deleted?

Warren & Preben, thank you for your quick answers.

I was running fossil ui on a separate port from the instance of fossil server.

fossil ui hosts all known repos and runs under my account.

fossil ui --errorlog /path/to/errors.log --port 8088 --repolist / --user 'Admin'

fossil server points to a subfolder and runs under an account without a shell and without a home directory.¹

Even when I quit the fossil ui instance I'm still seeing the yellow page on localhost & 127.0.0.1 but not on my IP address.

“cannot find current working directory; Permission denied” makes me think perhaps fossil is assuming a home directory to write a .fossil file in (because I'm accessing locally.

Is this the case?

Checking this in the source code is bit too much for me now. (And setting up fossil as a cgi is also a bit too heavy for my needs.)

Thank you for your thoughts.

---

1. ^{^} This is for hosting to lesser trusted people and places.

Possibly this might be avoided if one could provide “unix:/path/to/socket.sock” in place of an IP address.

I know it's not exactly across every platform but from what I've heard that option affords better data protection by using file system permissions and avoiding IP packet analyzers.

Thus the program in front of fossil and fossil can communicate in private.

Feature request I guess. :-)