Of course, after than, whatever you’ve just plugged into it, will most likely not work

502 Bad Gateway
504 Gateway Timeout
X-Forwarded-For

The solution is probably somewhere deep in the bowels of whatever you’re trying to make work

It will look obvious once you’ve figured out, that’s why it wasn’t mentioned next to the bunch of instruction you pasted into your console to install the thing

Just another day walking in the forest of papercuts

  • haych@feddit.uk
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    I can’t say I’ve ever had that problem. The 80 is grey so it’s clear it’s an example and not actually filled out. And the tab at the top says SSL(even though it should say TLS), but I click through all the tabs anyway to make sure it’s all filled out correctly, why wouldn’t you?

    • Creat@discuss.tchncs.de
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 month ago

      80 being grey suggests it’s the implicit default, not an example. Like in any other input mask like this. That is a very reasonable company and not intuitive at all.

      • Zeoic@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        Grey text has always been a hint / tip / example, why would it be an implicit default?

        • Creat@discuss.tchncs.de
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          always […] why would it be an implicit default?

          Cause that’s what I intuitively expected, because in the tools that I use daily, that how it is there. Here are some examples of other administrative web interfaces that use grey to show you the implicit default that I happen to have running and could find in like 3 minutes. So much for your overconfident “always”:

          • Proxmox PVE or PBS. Basically every dialog. Example network interface configuration: example
          • TrueNAS, example “Add Dataset”
          • OPNsense, example “Firewall Rule”, the destination port range has an implicit default and is grey:

          Note: I’m not talking about a form to fill in your name with “john doe” or whatever, and even that I can’t even remember seeing either. Cause it just says “Name:” and nobody needs an example.

          • Eager Eagle@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            Those TrueNAS fields seem gray because they’re disabled (since it’s inherited), not because those are defaults.

            • Creat@discuss.tchncs.de
              link
              fedilink
              arrow-up
              0
              ·
              1 month ago

              Yea I realized that only after. I agree it’s slightly different from the grey text in text fields, but it still illustrates the point because it’s also an implicit default value (that happens to be unchangable in this context). So it kinda applies, but yea not quite the same.

            • interdimensionalmeme@lemmy.mlOP
              link
              fedilink
              arrow-up
              0
              ·
              1 month ago

              inherited versus default, that is kind of splitting hair when we’re talking about user interface.
              Here the gray means “this is what it’s going to be if you don’t write something else here”

              • Eager Eagle@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                1 month ago

                Disagree. When it’s inherited, the gray value is not applied, because it’s defined somewhere else. It’s not a default in this case.