[NV-1244] 🐛 Bug Report: UI making requests to localhost when deployed on remote server

[SpencerMiller23]

📜 Description

The first issue is that the console hangs on the line reading Attaching to ws, api, web, widget, embed. In addition, when trying to sign up, I get a message reading "Network error".

👟 Reproduction steps

1. Setup a new remote server with the appropriate SSH keys (I'm using Digital Ocean)
2. Create a docker context for the remote server and change the current context to use it
3. Run docker-compose up
4. Note: I also changed all the variables in the .env file to use the IP of my server and the problem persisted

👍 Expected behavior

Start all the containers on the remote server

👎 Actual Behavior with Screenshots

I checked the Network tab of Chrome dev tools and I can see that the requests are being made to localhost and not my IP (even after updating the URLs in the .env file.

💻 Operating system

Linux

🤖 Node Version

v16.14.0

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to submit PR?

No response

_NV-1244

[djabarovgeorge]

Hi @SpencerMiller23 Thanks for bringing up the topic. If I understand correctly you host the services remotely, to better understand I would like to raise a few points.

1. Can you verify that the .env file is located in the same directory as the docker-compose.yml file?
2. Could you try hosting up the docker environment locally and see if it works for you?

[SpencerMiller23]

Hey, @djabarovgeorge thanks for getting back to me. I can confirm both that the .env file is located in the same directory as the docker-compose.yml file and that hosting the docker environment locally works as expected.

[djabarovgeorge]

Hey thanks for looking it up. Strange the last thing i could suggest checking is to connect to the service and validate if environment variables were updated, however, I am not sure the issue is there.

@scopsy @davidsoderberg do you have any insights on the matter?

[techsavvyash]

Hey, I would like to take this up.

[3576892]

Em seg, 3 de out de 2022 08:06, Yash Mittal @.***> escreveu:

Hey, I would like to take this up.

— Reply to this email directly, view it on GitHub https://github.com/novuhq/novu/issues/1255#issuecomment-1265217247, or unsubscribe https://github.com/notifications/unsubscribe-auth/A27D42UI56T3VK7X6LZ5JT3WBKV2RANCNFSM6AAAAAAQLR4D6Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[jainpawan21]

Hi @techsavvyash Are you still interested in working on this issue Do you know how to approach this?

[techsavvyash]

Hey @jainpawan21, yeah I am still interested in working on this, As of now, I have a hunch on how to approach this but I am still starting out so will have to give it a go, but I am pretty sure, I'll be able to handle this.

[SpencerMiller23]

Hey @techsavvyash how's it going? Any updates for us?

[oba2311]

Hi, @iampearceman coud you help us understand who's working on this? thanks

[oba2311]

@techsavvyash thanks for your intention - it's been quite some time and we want to get this done and therefore will take this one home and execute soon with the team. Thanks!

[scopsy]

@SpencerMiller23 tried to replicate this but without a lot of luck, is this is something you encounter? If yes, will do a deep dive with the team about it.

[scopsy]

I think we found a similiar issue and resolved it as part of 0.11.0, if you could take a look at this again with the new version. Closing this issue for now.