When I'm accessing unmenu remotely via a vpn, half of the hyperlinks are not correct. Some links point to "http://tower:8080/..." (these are unusable remotely) and some point to "http://tower.fully.qualified.domain.name:8080/..." (these work fine).

IIRC the top menu has only local links and individual pages have mostly fully qualified links.

 

The issue doesn't exist with local access - both links will resolve to the same machine, so I didn't even know the problem existed until I've tried to access my server remotely.

Googling this forum hasn't revealed similar threads.

then fix it.  You have the source AND a VPN, I do not have a VPN.

 

Sounds like you need to just fix your domain name server and not rely upon net-bios.

 

Joe L.

Works fine here with openvpn hosted on my router and accessed from a winxp client. What vpn configuration are you using? It almost sounds like something is being routed through a proxy that is rewriting the urls incorrectly.

then fix it.

 

Fixed - the problem was that somehow (probably during the upgrade) the server reverted to the default name 'Tower', instead of tower.home

Fixed the config, restarted and everything works!

 

Grrr... I feel like a fool now - I should've spotted capital T in Tower. It was in front of my eyes all the time

ok im still new to unraid and am trying to figure this out also.  i am not using a vpn, just remotely by port forwarding them.  the links just turn to tower after the link is pressed. 

ok im still new to unraid and am trying to figure this out also.  i am not using a vpn, just remotely by port forwarding them.

If you value your data and your network, I would pull the plug on your outside access NOW, and remove the port forwarding. Unmenu is NOT designed to be exposed to the outside world, and can NOT be secured as written.

ok im still new to unraid and am trying to figure this out also.  i am not using a vpn, just remotely by port forwarding them.

If you value your data and your network, I would pull the plug on your outside access NOW, and remove the port forwarding. Unmenu is NOT designed to be exposed to the outside world, and can NOT be secured as written.

A fool and his data are soon parted....  :'(    A VPN is mandatory for any remote access.  unRAID itself is not secure, and unMENU certainly cannot ever be.

 

If you've not already been hacked, just give it a few more hours.  It is not a matter of "if", just "when"

 

Joe L.

ok im still new to unraid and am trying to figure this out also.  i am not using a vpn, just remotely by port forwarding them.  the links just turn to tower after the link is pressed.

Your unraid box needs to know your fully qualified DNS name, not just 'tower'. Please, please think carefully before doing that - as others have written, you can be hacked within hours if you leave open unsecured ports forwarded to your Unraid box. If you don't know how to setup a VPN then you shouldn't really be exposing vulnerable Unraid to the 'elements' of the modern internet.

As you can see if different places of Unraid documentation: You have been warned.

 

Jerry1111

 

Would that also include ports opened for iStat (5109) so remote monitoring can be done from afar.  Should I shut of port forwarding of port 5109?

Would that also include ports opened for iStat (5109) so remote monitoring can be done from afar.  Should I shut of port forwarding of port 5109?

I don't know if iStat has any vulnerabilities, so I can't say one way or another. Port forwarding is always risky to some extent or another, if the app listening on the open port has vulnerabilities, chances are you will be hacked sooner or later. Best to say don't do it unless the application is designed from the ground up for exposure to the internet in general, like a VPN server, or a properly configured and maintained web server. iStat may be fine, may not be. In general, if you don't know and had to ask, you shouldn't expose it until you do know for sure.