3
dakkarant
46d

NGINX sucks donkeyboner... hardcore...

Comments
  • 17
    I am sorry but I have to disagree
  • 3
    I mean, it's okay. It's not quite as load tolerant as other things, but it doesn't crap the bed or anything.
  • 0
    @lamka02sk the documentation to set up config for a reverse proxy is non existent, ive been trying on and off for months now to get websockets working and i cant find anything on it
  • 3
    @dakkarant hm. Honestly...

    It's not hard. Where is your problem?

    Detailed information, please.

    I'd understand it for many things ... But a reverse proxy?

    Quite easy as long as you don't have requirements that are hard to implement.
  • 0
    @lmgtfy nginx reverse proxy setup
  • 0
  • 0
    @IntrusionCM i got a vps, running plesk, on that same vps im running docker, that is running a container, that container automagicly configures proxy rules to forward it to a domain.

    port 8080 works fine, but it always fails when trying to use a websocket
  • 1
    @dakkarant there are many reasons why this could fail.

    Most of them are not specific to NGINX.

    Have you tried a tcpdump analysis from both sides of the connection? Wireshark is essential in figuring out wether it's an TCP or OS or userspace issue.

    IPv4 only binding of the socket in docker itself and assuring all communication happens in IPv4?

    Excluded anything security related, especially inside the docker image?
  • 0
    @IntrusionCM I have no idea what to even look for, ipv4 only is all i can tell you
  • 1
    @dakkarant it's highly unlikely that everything is IPv4.

    Everything is at least partially IPv6 nowadays unless you explicitly deactivate it.

    You might use only IPv4 addresses.... But sockets are by default IPv6.

    I'd highly rate you to try the reverse proxy first from inside docker, eg by manipulating the image and testing inside the machine.

    If that works, start with tcpdump to find out where it goes wrong.

    If you need help. You could share the dumps if there's nothing concerning security
  • 0
    @IntrusionCM i have no clue how to manipulate an image to get inside docker, i can give you an inspection dump i guess
  • 0
    @IntrusionCM if you or anyone can figure out how to get a Hasura container working with websockets on a vps with nginx, not locally, id be very grateful
  • 3
    It’s better than most.
    I agree about the configuration having some learning curve, though. And debugging complex configurations can get tiring.

    But again, it’s much better than most alternatives.
  • 1
    Try caddy.
  • 0
    @dakkarant have you enabled sticky sessions?
  • 1
    @dakkarant Them I'm honestly really wondering what you're searching for. I had my first reverse proxy with nginx setup within minutes thanks to ddg'ing around 😄
  • 0
    @linuxxx ive tried every solution i found on the first 3 pages of google seaching for "nginx websockets" and i just cant get it working
  • 0
    @dakkarant I'm wondering if search engines would make the difference in this case? I don't use Google but duckduckgo, maybe give it a try?

    At least a few of these results seem credible:

    https://duckduckgo.com//...
  • 0
    @linuxxx all the same results
  • 0
    @dakkarant What exactly is going wrong? Because the documentation in some of the results of the DDG link is actually correct
  • 0
    @linuxxx 404 for the wss links
  • 0
    @dakkarant You mean when you literally visit them in your browser?
  • 0
    @dakkarant wtf are you doing with browser? You do understand that websocket and http are different protocols?
  • 0
    @linuxxx no when a component that uses a websocket connection tries to connect to the server's
  • 0
    @dakkarant I'd honestly need to see the server/configs because this seems like something is wrong... But, I have way too much on my plate too badly :/
Add Comment