First, thank you for making this. Seems very useful.. That being said I'm having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.
services:
mixarr:
container_name: mixarr
image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0
ports:
- 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container
- 3443:443
volumes:
- ~/mixarr-data:/data
environment:
- SESSION_SECRET=$(openssl rand -hex 32)
- FRONTEND_URL=https://my-domain:3443/
- BASE_URL=http://my-domain:3010/
restart: unless-stopped
Edit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don't need it built in.
That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.
Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.
It's okay to be bad at games without bashing people who are better at games. Many of us worked through covid, and are still working believe it or not, and were still able to beat difficult games.
Watched 14 Peaks last week and when they got to Mount Everest, there was a literal line of like 100+ people queued all the way up to the top of the mountain.
How many of those are through add-on deals like they offer through Verizon? I'm curious how discounted it is through them (some plans offer Disney+ for "free" I believe) and how much that inflates the subscriber rate.
You can pretty easily point Lidarr to an alternate cache server. Either use the docker images they provide (link below) or of you already have Lidarr with plugins setup, you can do it that way (also explained in the link below)
Do you also think the engine that comes with your car is free because the manufacturer doesn't sell it as a separate item and it's not listed on the receipt?
Edit: His answer proves he's just a troll. Weird thing to troll about though but I don't judge what someone gets off to ¯(ツ)_/¯.
First, thank you for making this. Seems very useful.. That being said I'm having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.
services: mixarr: container_name: mixarr image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0 ports: - 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container - 3443:443 volumes: - ~/mixarr-data:/data environment: - SESSION_SECRET=$(openssl rand -hex 32) - FRONTEND_URL=https://my-domain:3443/ - BASE_URL=http://my-domain:3010/ restart: unless-stoppedEdit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don't need it built in.
That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.
Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.