Issues when using DNS name instead of IP of server #20
Comments
|
Hello. Can you provide your config file (without the smtp passwords). Thanks, |
|
Hi Pablo, Cheers, |
|
Hello. Can you try the option "use_client"? That should fix the issue. This option makes the browser to not use an absolute path when accessing resources from the server. |
|
This worked, thanks! Wouldn't it make sense to make this the default config and put this modified config as default in the docs? One could also add that info to the explanation of "use_client". I'd be happy to help with a pr but it looks like the docs are not in this repo? This issue can then be closed. |
|
Oh, I just tried the reverse proxy (apache), this is still not working with "use_client", maybe related to the DNS/IP issue, not sure, should I open a new thread? edit: More details... If you need, I can post again more, like the ./server.js logs. |
|
Sorry for the late reply. I'll try to replicate the issue and let you know if I succeeded. And yes, it makes sense to have this option as the default. I'll try to update the code :) |
|
Using NGINX as SSL proxy emerges new problems. I have tried to fix it but nothing works: Without use_ssl the connection is x origin failed |
|
Sorry for the late reply. This is a working nginx sample configuration (I've removed parts that I don't think are strictly needed) There are two endpoints in networkmaps that are websockets and need special handling in nginx: user and diagram. I suppose this is what is failing on your setup. Let me know if this helps you in setting up your reverse proxy. |
|
Hey, |
|
Thanks Pablo! edit: I was not interested in using https so far, but trying it out shows there still seems to be an issue with that. I just used the posted config without the ssl parts and listening on port 80. When I switch to TLS, I just get a blank screen in the browser. The connection is secured, so certificates are working. I can provide logs and try to help figure this thing out, if there's a need. Levvy or Pablo, what do you think? |
Describe the bug
When I call networkmaps with its IP it mostly works well but as soon as I use the DNS name, I cannot load network maps correctly. There are popping up some errors in the UI with something closed and "Error loading definition file for shape group 5. Connection error." and sometimes also other groups, e.g., "Error loading definition file for shape group 2. Connection error." One cannot see anything in a new diagram, in an existing diagram one sees only some cubes instead of the correct devices.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When I call the server via its DNS name instead of its IP it should work exactly the same way as when IP is used.
Desktop (please complete the following information):
Additional context
networkmaps is running on a dedicated testing VM on proxmox, there's nothing else on it. VM is debian 11 bullseye with node v12.22.5. Tested on other machines as well, issue seems to be server-related. I also tried using an apache reverse proxy without any improvements. I also tried to provide the dns name instead of IP in the config "address" field to no avail.
The live log reads as follows:
Please let me know if you need further details.
The text was updated successfully, but these errors were encountered: