Proxying WebSockets with NGINX

Sdílet
Vložit
  • čas přidán 12. 09. 2024
  • Learn how to set up NGINX as a reverse proxy for WebSockets or SocketIO app.
    ------------------
    Deploying Node playlist:
    • Deploying Node

Komentáře • 61

  • @ishanksharma9051
    @ishanksharma9051 Před 6 lety +19

    This series need to be spread around , great work

  • @oranbenavi8105
    @oranbenavi8105 Před 5 měsíci +1

    I've spent 2 days trying to find a solution to my error, even chatgpt failed to help.
    Thank you so much you video help me a lot 🙏🙏🙏

  • @colbr6733
    @colbr6733 Před 2 měsíci +1

    This is excellent. I've been looking to better understand what is going on with WebSockets and Nginx. This is certainly one of the best explanations available on you tube, most simply say copy this code and paste it into locations.

  • @kunah5250
    @kunah5250 Před 3 lety +1

    Broooo you're the king, i literally spent an evening trying to host my ws server, and i finally found your video, thank god, you saved me, ilusm bro ❤

  • @khalidelgazzar
    @khalidelgazzar Před rokem +1

    Really great video. Love showing the dev tools and different network options (web sockets, XML ajax requests)

  • @yassin_eldeeb
    @yassin_eldeeb Před 3 lety +1

    Thank you so much, You don't know how I spent the last 7 days in nightmare with that problem, Finally I found you, You deserve more than a subscribe and a like.
    P.S: Do you have a Patreon or something like that you must get at least some appreciation.

  • @smartliga8623
    @smartliga8623 Před 6 lety +3

    So much times you saved me a lot of time. Thank you for socket error handling

  • @thatoyaonebogopa9483
    @thatoyaonebogopa9483 Před 2 lety

    Gread short snippets. Easy to digest. Love it.

  • @silvesterlangen164
    @silvesterlangen164 Před rokem +1

    Thank you for showing how to configure it. This saves me hours of work. :-)

  • @denial3874
    @denial3874 Před 4 lety +3

    failed: WebSocket is closed before the connection is established.

  • @dawid_dahl
    @dawid_dahl Před 3 lety +1

    I love this video series! Please make more things like this! :D

  • @oszy6069
    @oszy6069 Před 4 lety +3

    Hi! what if you want websocket to listen in a different socket but keep website on socket 8080?

  • @skob
    @skob Před 5 lety +3

    Спасибо, очень выручили!
    Thanks, really useful video!

  • @josedizon7389
    @josedizon7389 Před 2 lety +1

    It worked!! thanks bro

  • @JustLookA7
    @JustLookA7 Před 4 lety +1

    Life saving video. Thank you very much :)

  •  Před 2 lety

    Thanks! Simple solution and very well explained

  • @hillside_coder
    @hillside_coder Před 4 lety +1

    Can you do this with an another Node process, over a different port....Or it needs to be 8080? Is it possible for example to have another location block, where you would proxy pass websocet connection , over maybee 4000?

  • @adityakulkarni2472
    @adityakulkarni2472 Před 3 lety +1

  • @guilhermeninov8536
    @guilhermeninov8536 Před rokem

    You saved my life!

  • @elmasx
    @elmasx Před 8 měsíci

    Thank you so so much!

  • @ericktucto
    @ericktucto Před 2 lety +1

    Muchas gracias me ayudaste a configurar mi servidor php para usar con websocket y asi hacer un chat real-time

  • @mauroteixeira3885
    @mauroteixeira3885 Před 10 hodinami

    Genius!

  • @ehsanmohiti3071
    @ehsanmohiti3071 Před 4 lety

    Good Job man. thanks.

  • @webgooniedotcom
    @webgooniedotcom Před 4 lety

    I think you just helped me out tremendously. I use application manager for jump starting my node application which support showed me. However it doesn't work with websockets on my socket.io app that I have. I have many php applications running and don't want to disturb them so doing ngnix would need to be not disturbing my apache applications. I did your video earlier and killed all my php applications so I have ngnix installed but it's disabled. How can I do this same process just on apache to get websockets work. I have been looking for months and this is the closet video I could find even touching basis on my most biggest hurdle in development yet. It has halted all my nodejs applications because webrtc is the only reason I want to use node and because I can't get sockets configured on my centos 7 machine I have stopped for over 6 months now. Please advise you or anyone.

  • @JimmiJohnJunnior
    @JimmiJohnJunnior Před 5 lety

    I have set mqtt connections to the same path as my website but with different ports, how would I go about solving that?

  • @JonathanPohlner
    @JonathanPohlner Před 5 lety

    you said you'd post the config file? Is it on another video?

  • @TusharBorawake
    @TusharBorawake Před 3 lety

    Hi, I am facing issue in same scenario. Could you please guide me in this. I have react application which connects to tomcat server using nodejs server. On server all the API logic is implemented and now I want to implement websocket which will first connect to node server then tomacat server. I just know the there should be a tunneling logic needs to be implemented but I don't know how to do that. Could you please help me in this.

  • @RdozeTV
    @RdozeTV Před 3 lety

    What if have ssl and i want to do using wss

  • @sandeepdubay2204
    @sandeepdubay2204 Před rokem

    Super tutorial

  • @eyalpery8470
    @eyalpery8470 Před 2 lety

    Thank you!

  • @mystery7546
    @mystery7546 Před 5 lety +4

    Can you Create a Video about deploying the socket.io app in the server using node and react from scratch

  • @tfaimummy
    @tfaimummy Před 6 lety

    on port 80 io was run but I have CORS issue when ssl is activated? can you help me please!

  • @matejmaloca1000
    @matejmaloca1000 Před 7 lety +1

    How diffrent is configuration if we are working with https/2?

    • @JuriyBura
      @JuriyBura  Před 7 lety +2

      To be honest I have never tried it in production, however it looks like Nginx has "http2" flag that should make things "just work". The server configuration block should look like "listen 443 ssl http2 default_server;" to have both SSL and HTTP2. Disclaimer: haven't tried it and don't know if it will work :)

    • @matejmaloca1000
      @matejmaloca1000 Před 7 lety

      Thanks for getting back to me.

  • @ehsankhorasani_
    @ehsankhorasani_ Před 4 lety

    Thanks for your awesome videos
    I have a graphql nodejs server which have just one endpoint. So how can I set up both http and websocket on one location. Because graphql only have one endpoint

    • @RK-gm4pd
      @RK-gm4pd Před 4 lety

      how about
      import { WebSocketLink } from "apollo-link-ws";
      import { HttpLink } from "apollo-link-http";
      import { split } from "apollo-link";
      import { getMainDefinition } from "apollo-utilities";
      const httpLink = new HttpLink({
      uri: "hasura-infiite-loader.herokuapp.com/v1alpha1/graphql" // use https for secure endpoint
      });
      // Create a WebSocket link:
      const wsLink = new WebSocketLink({
      uri: "ws://hasura-infiite-loader.herokuapp.com/v1alpha1/graphql", // use wss for a secure endpoint
      options: {
      reconnect: true
      }
      });
      // using the ability to split links, you can send data to each link
      // depending on what kind of operation is being sent
      const link = split(
      // split based on operation type
      ({ query }) => {
      const { kind, operation } = getMainDefinition(query);
      return kind === "OperationDefinition" && operation === "subscription";
      },
      wsLink,
      httpLink
      );

  • @Microchaosmac
    @Microchaosmac Před 6 měsíci

    thanks

  • @speckygaming8499
    @speckygaming8499 Před rokem

    can anyone help me i making a microservice to handle 50k concurrent request on node js and socket io i want to divide the load on multiple connection and those connection should not close or die when user leave all 50k connection should me maintaind

    • @JuriyBura
      @JuriyBura  Před rokem

      Hmm, not quite sure how this is supposed to work though. If the user leaves and closes their side of the connection, the connection will be closed.
      Overall, I would recommend looking at something that has auto-scaling, for example AWS API Gateway + Lambdas, if the load is spiky and you need elasticity.
      For experimental purposes I found this article insightful: unetworkingab.medium.com/millions-of-active-websockets-with-node-js-7dc575746a01

  • @user-os4yb9tg6w
    @user-os4yb9tg6w Před 5 lety

    thank you, Юрий

  • @jhonysou
    @jhonysou Před 5 lety

    I saw that you used port 80, if I'm using ssl do I need to set 443 right ?

    • @JuriyBura
      @JuriyBura  Před 5 lety +2

      Jhony Souza right, but setting up SSL is a bit more complex than that. There’s another video about it in a playlist.

    • @jhonysou
      @jhonysou Před 5 lety

      @@JuriyBura Thanks very much !

  • @nikhilverma4976
    @nikhilverma4976 Před 5 lety

    How come its okay to run all nginx related tasks as root but switch to a different user when working with pm2/node.js

    • @JuriyBura
      @JuriyBura  Před 5 lety +1

      nginx is executed as user "nginx" it also has very limited permissions. When you run > systemctl start nginx, the script switches from "root" to "nginx" user if that makes sense.

  • @cursorhigh
    @cursorhigh Před rokem

    bro plz tell us for https
    and wss

  • @AkamiChannel
    @AkamiChannel Před 3 lety

    How to do all this with ssl is what confuses me.

  • @jack82822005
    @jack82822005 Před 5 lety

    How could I know if the version of http is 1.1?
    thanks!!! >

    • @JuriyBura
      @JuriyBura  Před 5 lety

      What do you mean by that? How do you make sure that the browser is indeed using HTTP1.1?

    • @jack82822005
      @jack82822005 Před 5 lety

      I mean at 4:33, you set "proxy_http_version" as 1.1 , but how do we get that number?

    • @JuriyBura
      @JuriyBura  Před 5 lety

      @@jack82822005 we don't :) we choose which HTTP version will proxy use. 1.1 is currently the most reasonable choice. The other option would be 2.0, but HTTP2 is a whole different story. Don't worry, HTTP 1.1 was released in 1997, so everything supports it.

    • @jack82822005
      @jack82822005 Před 5 lety

      Oh OK I see!!
      so we use HTTP 1.1 in most case, right?
      Will you create another video to talk about HTTP 2? XD
      Thanks so much

  •  Před 2 lety

    Ty but how to do this as https?

  • @horlacsd
    @horlacsd Před 4 lety

    spacebo moi brat

  • @Douglas-Heffernan
    @Douglas-Heffernan Před 3 lety +1

    I _ L O V E _ U _ S O _ M U CH _ !
    i struggled since 2 Days with my Ubunto 18.04 Server and Polling. Now i have a great WebSocket-Connection and my game runs sooooo smooth now

  • @khalidelgazzar
    @khalidelgazzar Před rokem

    Really great video. Love showing the dev tools and different network options (web sockets, XML ajax requests)

  • @khalidelgazzar
    @khalidelgazzar Před rokem

    Really great video. Love showing the dev tools and different network options (web sockets, XML ajax requests)