10

Me: "Oh right I still had to fix that"
Me: *fixes thing*
Me: *checks on staging to make sure it all works*
Thing: *works absolutely fine*
Me: "Cool, let's promote it"
Me: *updates production stack*
Me: *checks on production to make sure it works*
Thing: *still broken*

dsfhjh dsaghdsaupot nvhudfot vnhgue

Comments
  • 0
    Cache? :P
  • 2
    @alexbrooklyn No, apparently Traefik doesn't like it when I don't specify that a certain url can also be accessed without "www"...

    This is what I had:

    ```

    (Host(`www.finlaydag33k.nl`) && PathPrefix(`/pma/`))

    ```

    this is what fixed it:

    ```

    ((Host(`www.finlaydag33k.nl`) || Host(`finlaydag33k.nl`))&& PathPrefix(`/pma/`))

    ```

    Not afraid of showing that stuff here, one can find it on my Git anyways XD
  • 0
    @FinlayDaG33k how different is staging from prod ?
  • 1
    @dder Outside the specification of the Host in the Traefik config (eg. "www.finlaydag33k.nl || finlaydag33k.nl" vs "testing.finlaydag33k.nl") and the database password they are pretty much identical.
  • 0
    Damn that.
    Load ? Maybe it’s a load balancing problem...
    But very good setup, if they are so identical! Let me tell you, it’s not always the case!
  • 1
    @dder No, somehow the issue was that it was missing an (albeit irrelevant) host definition for the proxying... no clue why that was tho...
Add Comment