Is your linter configured for JSX? Please share any config options that you have set.

Nginx path forwarding seems to be working fine now: jermasearch.com/internal-apidbtest works correctly. Even though port 3030 still connects to nginx, it shouldn't be necessary to deploy your app. I would suggest adding a forward slash to the url though

I really don't know why nginx isn't on port 3030, and if you don't have ssh access, it's hard to debug. Your nginx config should leave it open, but trying to run the backend on a different port would be worth a shot. To find the exact reason that node-server is failing you'd need to somehow check it's logs. I'm not familiar with supervisord, but it should have some log format. Your react-app is also failing, the reason it works is because of how nginx uses the build files, to serve the code rather than forwarding port 3000. You can check the Server header to see if you're using nginx.

I do most of my work in WSL, so I like to keep a different theme telling me which env I'm in.

Here's a simple example: gist.github.com/Aarav-Juneja/5c9d9a83b5638d7cb4c9978a0f1ec89‌​8 I commented out a potential system using socket.rooms

Due to the nature of how disconnections work, you can't send any data. One last thing you can do, is try setting the room id as field socket.currentRoom = roomId, and then refer to this later, but you have to use some data from before the event.

If the user is in the current room, you can use socket.rooms to find the room.

What do you mean by it doesn't work? Is it printing an incorrect URL or is there an issue with viewing the webpage? The issue may be related to your usage of req.url rather than req.originalUrl

I'm not the most experienced with express router, but I believe that each route requires it's own router. It could be that the auth route is using the router. Perhaps code like const blogs = require('./routes/blogs')(express.Router()); would work better?