N
Novu3mo ago
Sang Dang

What is the socketUrl for account in EU?

Hi, I try to look around the documentation but so far only found this place: https://docs.novu.co/echo/sdk/client And it took me several hours to realized that I have to specify the backendUrl if my account is in EU. This should be mentioned in the quick start guide. Now it works but not real time, every new notification need a full refresh app in order to see, so I guess I also need to specify the socketUrl for it? Could someone help me with this? I can not find it in our doc, or github issues and Google also return all default settings. Thanks.
6 Replies
Ask Inkeep
Ask Inkeep3mo ago
Hi @Sang Dang, I'm an AI assistant for Novu. While a team member reviews this question, I'll look through relevant sources and see if I can provide suggestions. Please tag @Ask Inkeep with any follow-up questions. ----------------------------- While I generate an answer, here are some sources that might be helpful: * Configuration * How to use Novu to send notifications to a channel in a Discord server * React Get Started * Zulip -----------------------------
Ask Inkeep
Ask Inkeep3mo ago
Answer For configuring your Novu account in the EU region, you've correctly identified that the backendUrl needs to be specified. While the documentation provides clear guidance on setting the backendUrl to https://eu.api.novu.co for EU-based accounts, as seen here:
const echo = new Echo({
backendUrl: 'https://eu.api.novu.co',
apiKey: '<YOUR_NOVU_API_KEY>',
devModeBypassAuthentication: false,
});
const echo = new Echo({
backendUrl: 'https://eu.api.novu.co',
apiKey: '<YOUR_NOVU_API_KEY>',
devModeBypassAuthentication: false,
});
(1) However, regarding the socketUrl for real-time functionality, the current documentation and information provided do not explicitly mention a distinct socketUrl for the EU region. Typically, the socket connection for real-time updates should work seamlessly once the backendUrl is correctly configured, implying that the socketUrl might not need manual configuration or could follow a similar regional adjustment pattern to the backendUrl. Since the exact socketUrl for the EU region isn't specified in the provided documents, I recommend ensuring that your backendUrl is correctly set to the EU endpoint as you've done. If real-time notification issues persist, it might be beneficial to review the setup or configurations related to real-time event handling in your application, or reach out to Novu support directly for guidance on the socketUrl for EU accounts, as specific regional socketUrl configurations might not be publicly documented at this time.
Ask Inkeep
Ask Inkeep3mo ago
Got it. Tagging @Support for additional help.
Sang Dang
Sang Dang3mo ago
I made a guess from the default url, and look like it works now:
socketUrl="https://eu.ws.novu.co"
socketUrl="https://eu.ws.novu.co"
Please, add this into the documentation.
Pawan Jain
Pawan Jain3mo ago
@Sang Dang Thanks for the feedback. We will add it in the docs
Sang Dang
Sang Dang3mo ago
Thanks @Pawan Jain 🙏 really appreciate it