• 1 Post
  • 41 Comments
Joined 3 years ago
cake
Cake day: June 27th, 2023

help-circle
  • 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.


















  • First, kernel level anti cheat is more akin to a business owner installing very invasive cameras, on your person, and they watch every little thing you do, including going to the bathroom. If they see something they don’t like, you gtfo of their store. Don’t know about you, but I wouldn’t willingly agree to go into a store like that.

    Second, in a game like battlefield… Who cares if someone is cheating? It’s not a competitive shooter like CS or Valorant. If someone is cheating, change servers…

    If you really care about cheating that much, get a console. Stop giving these companies the okay to install rootkits on your PC.