Closed pm974 closed 1 year ago
Please use correct issue titles. We cannot smell its about snipeit.
Please use correct issue titles. We cannot smell its about snipeit.
Done.
I wonder how much you searched and then checked the I've checked all open and closed issues and my issue is not there.
Duplicate of #8886
App Name
snipe-it
SCALE Version
22.12.0
App Version
6.1.0_7.0.24
Application Events
Application Logs
Application Configuration
env
IMAGE_LIB=gd REDIS_PORT=6379 KUBERNETES_SERVICE_PORT=443 KUBERNETES_PORT=tcp://172.17.0.1:443 DB_CONNECTION=mysql HOSTNAME=stock-snipe-it-6b4688bb48-ffxx8 USER_ID=568 APP_URL=http://localhost:80 DB_PORT=3306 API_TOKEN_EXPIRATION_YEARS=40 HOME=/root UMASK_SET=2 DB_DATABASE=snipe-it PGID=50 MAX_RESULTS=500 SESSION_DRIVER=redis GROUP_ID=50 DB_USERNAME=snipe-it ENCRYPT=false LOGIN_LOCKOUT_DURATION=60 QUEUE_DRIVER=redis CACHE_DRIVER=redis TERM=xterm KUBERNETES_PORT_443_TCP_ADDR=172.17.0.1 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin GID=50 KUBERNETES_PORT_443_TCP_PORT=443 KUBERNETES_PORT_443_TCP_PROTO=tcp SECURE_COOKIES=false EXPIRE_ON_CLOSE=false FILESYSTEM_DISK=local LOGIN_MAX_ATTEMPTS=5 PUID=568 COOKIE_NAME=snipeit_session UID=568 SESSION_LIFETIME=30 APP_TIMEZONE=Europe/Brussels UMASK=2 REDIS_PASSWORD=secret KUBERNETES_SERVICE_PORT_HTTPS=443 KUBERNETES_PORT_443_TCP=tcp://172.17.0.1:443 DB_PASSWORD=secret APP_ENV=production APP_KEY=secret REDIS_HOST=stock-redis KUBERNETES_SERVICE_HOST=172.17.0.1 PWD=/var/www/html NVIDIA_VISIBLE_DEVICES=void DB_HOST=stock-mariadb TZ=Europe/Brussels APP_LOCALE=en
Describe the bug
No matter what I input in the chart for APP-URL, the .env keeps returning APP_URL=http://localhost:80 preventing the application from working properly. This didn't happen in previous version 6.0.14. https://subdomain.domain.com/setup will redirect to http://localhost/setup making the process (and the upgrade) impossible. "Force TLS" not working as well as app PUID / PGID etc. -> it seems the hole chart isn't taking effect...
To Reproduce
Expected Behavior
The .env should reflect the deployment chart specified by the user.
Screenshots
Additional Context
If I force https://subdomain.domain.com/setup I can see the first setup page, but clicking the button to go to the next step will rediret again to localhost:80 making the process impossible to complete.
I've read and agree with the following