Can only access the app from http://localhost:3001/, not host IP address

[mccune68]

Bug Description

Sometimes I would like to be able to pull up Logarr on my phone while watching Emby so I can monitor logs, but it appears the app can only be accessed by the URL http://localhost:3001/, not, for example, the host IP address of the machine on my local network, such as http://192.168.1.20:3001/. You can access the login page from this IP address URL, but it won't let you login, it instead gives an error at the bottom of the page saying:

Login failed
NetworkError when attempting to fetch resource.

Steps to Reproduce

1. Go to the address http://192.168.1.20:3001/ in your browser while Logarr is running, where 192.168.1.20 is the local network's IP address of the host machine running Logarr.
2. Login using the credentials you have already established.
3. Logarr fails to login and gives the error noted above.

Expected Behavior

I should be able to access Logarr from a localhost address, from inside the same network using the 192.168.x.x address of the host running Logarr, or from 127.0.0.1 on the host machine itself.

Actual Behavior

You can only access it from the localhost address.

Deployment Method

Docker Compose

Version

0.6.1

Browser

Firefox

Relevant Logs

Additional Context

No response

[cahna]

This is not a bug. It could be considered a feature request for included proxies. You can add this yourself with an nginx container to handle mapping request paths to the appropriate port (frontend or backend).

For a feature request, a few options I can think of off the top of my head:

• Add vite proxy config to route /api requests to the backend container port during development
• Add nextjs api routes to route /api requests to the backend container port (negating the need for a vite proxy)
• Add an nginx container to docker-compose.yml to handle all traffic through a single port and route between the frontend and backend ports based on the request. I wouldn't want Logarr to add this because I deploy all webapps in my homelab behind a single nginx container that routes to services based on hostname and it would be silly to have multiple nginx instances running.

The nextjs api routes are probably what you want/need to get the service exposed as easily as possible through a single port.