toewen Posted May 11, 2021 Report Share Posted May 11, 2021 Website only accessible within my own network Proud to have launched my own website on my own server, but unfortunately it is only accessible within my own network. What could be wrong? apgw.synology.me Quote Link to comment Share on other sites More sharing options...
Chris Lloyd Posted May 11, 2021 Report Share Posted May 11, 2021 Look at the Synology documentation about making a site public. Quote Link to comment Share on other sites More sharing options...
MichaelM Posted May 11, 2021 Report Share Posted May 11, 2021 Do you already have a DYNDNS, so that your Synology-Server is accessible from Internet ? Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 12, 2021 Report Share Posted May 12, 2021 Maybe your router blocks the access from outside your LAN to your webserver. So you have to allow some router ports (80) to pass your routers firewall. For example Fritz blocks the routing to your components inside your LAN as standard security. My TNG runs from a Synology with DYNdns. Quote Link to comment Share on other sites More sharing options...
toewen Posted May 12, 2021 Author Report Share Posted May 12, 2021 Router port ok. Synology test now says: connection normal. Ik think it now works, but I have tot test outside my network. Quote Link to comment Share on other sites More sharing options...
toewen Posted May 12, 2021 Author Report Share Posted May 12, 2021 5 hours ago, Michael S said: Maybe your router blocks the access from outside your LAN to your webserver. So you have to allow some router ports (80) to pass your routers firewall. For example Fritz blocks the routing to your components inside your LAN as standard security. My TNG runs from a Synology with DYNdns. This is what I see in my router Should I change something here and what? Quote Link to comment Share on other sites More sharing options...
Ken Roy Posted May 12, 2021 Report Share Posted May 12, 2021 Web site url provided above On 5/11/2021 at 1:59 PM, toewen said: apgw.synology.me does not generate a clickable URL link in this forum nor on the TNG Wiki. Copying the URL and pasting it in a browser URL returns Quote Network Timeout The operation timed out when attempting to contact apgw.synology.me. The requested site did not respond to a connection request and the browser has stopped waiting for a reply. Could the server be experiencing high demand or a temporary outage? Try again later. Are you unable to browse other sites? Check the computer’s network connection. Is your computer or network protected by a firewall or proxy? Incorrect settings can interfere with Web browsing. Still having trouble? Consult your network administrator or Internet provider for assistance. there is a lot of work required to setup your own web hosting. I worked supporting and modifying the IBM mainframe operating systems for 33 years before I retired some 16 years ago and setting up my own web server is not something I would consider, since I also worked heavily with security. Too many security considerations and exposures. Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 12, 2021 Report Share Posted May 12, 2021 vor 5 Stunden schrieb toewen: This is what I see in my router Should I change something here and what? The first Possibility is on the Router: Do it with Poort forwarding IPv4. Another possibility is on your Syno: Under External Access at first DDNS. Then --> Routerconfiguration --> Setup Router. You can test if it works on your Synology account website: https://account.synology.com/ Maybe you have to read a little Quote Link to comment Share on other sites More sharing options...
toewen Posted May 13, 2021 Author Report Share Posted May 13, 2021 Can it be there is a problem with the port? As the website uses https port 5001 Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 13, 2021 Report Share Posted May 13, 2021 http://apgw.synology.me:64326/ it works with that port. The 5001 is only for your DSM, not for your webserver. Now you have to tell your router in the routerconfig to forward port 80 instead of 64326. But pay attention. After that your website and your webserver is accessible. Quote Link to comment Share on other sites More sharing options...
toewen Posted May 13, 2021 Author Report Share Posted May 13, 2021 Thank you, I remember that while setting up the ports, a message came up saying that some ports were busy and that another port had been chosen. Unfortunately, it did not say which port(s) it was. Now when I want to set the port manually I get the error message that there is a conflict with the current forwarding ports. Is it possible that I need to adjust something in the router? Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 13, 2021 Report Share Posted May 13, 2021 Sorry I didn't do that with EZ. But If you have a virtual host, you have to change that port first, or uncheck: Virtual Host. I would recommend to do it with Poort forwarding IPv4 on your router. Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 14, 2021 Report Share Posted May 14, 2021 Hey, you managed it? Oh no, something went wrong. Michael Quote Link to comment Share on other sites More sharing options...
toewen Posted May 14, 2021 Author Report Share Posted May 14, 2021 There seems to be a persistent conflict with setting port 80 via the EZ wizzard. Test with canyoyseeme.org gives no error messages. All ports are accessible from outside. Synology does not seem to know my router Experia Box V10 model H 369A and is not on the router list either. I have manually entered ports 80 and 443 in the router, but it remains a problem. Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 14, 2021 Report Share Posted May 14, 2021 What if you uncheck port 80. In EZ? Quote Link to comment Share on other sites More sharing options...
toewen Posted May 19, 2021 Author Report Share Posted May 19, 2021 Mission accomplished! Synology did not recognise my router and therefore could not forward the ports. I took a random router from the list, entered my router's access data, and the result was no error. Website is now online. Thanks for your suggestions. Quote Link to comment Share on other sites More sharing options...
Michael S Posted May 24, 2021 Report Share Posted May 24, 2021 Great 😅 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.