cannot get to website on my server internally after isp change

I have a synology nas ds411+ which i can access internally via its login page. I have a website that I made in joomla hosted on the ds411+.

the site is acousticlaptops.co.uk which i am told is working externally and i can get to the joomla login page via a mobile network so i think all that external infrastructure works ok.

Before my isp change i could access the webpage internally by putting the website address in the chrome browser.

now it just takes me to the router log in page.

how do i access the site internally now?

regards in advance
PeterBaileyUkAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zephyr ICTCloud ArchitectCommented:
is the webpage (management) of your Synology not on port 5000? E.g: <ip-of-your-synology:5000>

If it's not, maybe you can change it, so that it doesn't use the standard port 80 (if it is using it of course), you can normally change this under DSM Control Panel => Connectivity > Network > DSM Settings (I'm doing this out of my head, so I could be wrong) ...
0
PeterBaileyUkAuthor Commented:
yes i have access to that internally which i reach : http://192.168.0.185:5000/webman/index.cgi
0
DrAtomicCommented:
The website acousticlaptops.co.uk is being forwarded to acousticlaptops.no-ip.co.uk, can it be that you need to login to no-ip.co.uk to change the dynamic dns settings to reflect the isp change? Allthough that would imply external issues.

Do you see the website if you browse to http://192.168.0.185 or the internal ip equivalent of the website on the synology?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

PeterBaileyUkAuthor Commented:
thats all working correct the no-ip client runs at startup and has the correct ip address the .com and co.uk domains are forwarded correctly. its only internally now i cannot get to the sites which i need to, to update the sites etc.
0
DrAtomicCommented:
Also did you change your internal IP range with the ISP change over? Do you maybe have acousticlaptops.co.uk defined in your local hosts file pointing it to the ip address that is now the router IP?

DNS aside, are you able to access the websites on their internal IP addresses?
0
PeterBaileyUkAuthor Commented:
previously to changing isp i could put in the url and i could get to the joomla administrator log in. now internally it only takes me to the router login page but if i use the url on my mobile network i can get to the login screen of joomla
0
DrAtomicCommented:
Hi Peter,

If you access the website on your mobile network it does an outside-in connection; that works as intended as you said.

However if you access the website on your local network it uses the local (internal) IP address of the website (unless it's forced to somehow use the external website which leads to a hairpinning situation). This is why I was asking if you are able to correctly connect to the website if you directly connect to http://internalip. If you are able to pinpoint if you are able to access the website(s) on their internal IPs it will tell us that the issue is DNS related, if there is only one internal IP address (the router IP) then we need to check that the router isnt using port 80 on the internal side of the network and is thus blocking access to the webserver.

Basically trying to first make sure the websites are accessible on their internal IPs, then trying to figure out what changed and what was providing the FQDN service (i.e. local dns server, hosts file, router).

Ps. hairpinning is where you are trying to access an internal ip address from an internal ip address whilst going through the firewall (inside->outside->inside).
0
PeterBaileyUkAuthor Commented:
I am not sure what the syntax is to access the site internally i know the ip of the server is fixed @192.168.0.185 I know that currently the site is using port 80 on its virtual server of course that's from outside.
0
DrAtomicCommented:
Ah ok, no problem, you can always access a website through an ip address directly by using the following syntax in your browser:

[protocol][ipaddress][optional port number]

So in your case that would be:
http://192.168.0.185
(full syntax for completeness sake of the example http://192.168.0.185:80)

Does that display the website or the router page?
0
PeterBaileyUkAuthor Commented:
i have read that the router does not have nat loopback. could this be a part of the problem?
0
PeterBaileyUkAuthor Commented:
no http://192.168.0.185:80) takes me to the router login as usual.
0
Zephyr ICTCloud ArchitectCommented:
I know that normally when you browse to the ip-address of the Synology a redirect will bring you to the 5000-port address, this is a setting in Apache, it's supposedly also triggered when there's an issue with the website (when configured) on port 80.

So, the question would be, if the statement above is correct, what changed that would make Apache redirect to 5000 ... It supposedly looks for a "sample.php" file or something ... I'd need to read up on it again though ... Maybe it can help pinpoint the issue?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
PeterBaileyUkAuthor Commented:
my knowledge is not a lot on these infrastructure issues, I know that in the webservices section of the synology all website folders resolve to their no-ip equivalents on port 80 as attached.

The only change has been the router which is a zte h218n
ex1.JPG
0
PeterBaileyUkAuthor Commented:
ok got it.
0
PeterBaileyUkAuthor Commented:
thank you
0
akahanCommented:
Just turn off external management on the router.  It's intercepting your packets going to port 80, and presenting the router's own login screen, rather than allowing them through to the NAS.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Joomla

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.