[BUG] Uh oh! Snipe-IT thinks your URL is http://localhost:8080, but your real URL is http://localhost/setup Please update your APP_URL settings in your .env file

[nguamay]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

My file docker-compose i have set APP_URL=http://localhost:8080. When go to http://localhost:8080/setup show Error: "Uh oh! Snipe-IT thinks your URL is http://localhost:8080, but your real URL is http://localhost/setup Please update your APP_URL settings in your .env file"

Expected Behavior

No response

Steps To Reproduce

I'm running docker in Windows 10

Environment

- OS: Windows 10
- How docker service was installed:

CPU architecture

x86-64

Docker creation

version: '3'
networks:
    snipeit-network:
        driver: bridge

services:
    snipe-it:
        networks:
            - snipeit-network
        image: lscr.io/linuxserver/snipe-it:latest
        container_name: snipe-it
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Etc/UTC
          - APP_URL=http://localhost:8080
          - MYSQL_PORT_3306_TCP_ADDR=mysql
          - MYSQL_PORT_3306_TCP_PORT=3306
          - MYSQL_DATABASE=snipeit
          - MYSQL_USER=snipeit
          - MYSQL_PASSWORD=ppp@123
        volumes:
          - /path/to/data:/config
        ports:
          - 8080:80
        restart: unless-stopped
        
    mysql:
        networks:
            - snipeit-network
        image: mysql
        container_name: mysql
        command: --default-authentication-plugin=mysql_native_password
        restart: always
        volumes:
            - G:/database/:/var/lib/mysql
        environment:
            MYSQL_ROOT_PASSWORD: ppp@123
            MYSQL_DATABASE: snipeit
            MYSQL_USER: snipeit
            MYSQL_PASSWORD: ppp@123

Container logs

No

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[rdagger]

Having the same problem. I opened a new issue to hopefully provide more info.
#57