Services:Prerequisites: Difference between revisions
Minor update - troubleshooting guide: Prerequisites for Adding Services (7 sections) |
Major update - troubleshooting guide: Prerequisites for Adding Services (27 sections) |
||
| Line 1: | Line 1: | ||
Before adding a new service to the reverse proxy system, ensure you have the following: | Before adding a new service to the reverse proxy system, ensure you have the following: | ||
== Service Information == | == Service Information == | ||
= '''Subdomain name''' (e.g., <code>newservice.jb-vpn.uk</code>) = | === '''Subdomain name''' (e.g., <code>newservice.jb-vpn.uk</code>) === | ||
= '''Internal IP address''' (usually <code>10.8.0.2</code> for Synology NAS) = | == '''Internal IP address''' (usually <code>10.8.0.2</code> for Synology NAS) == | ||
= '''Internal port number''' (e.g., <code>8080</code>, <code>3000</code>, etc.) = | == '''Internal port number''' (e.g., <code>8080</code>, <code>3000</code>, etc.) == | ||
= '''Protocol''' (HTTP or HTTPS) = | == '''Protocol''' (HTTP or HTTPS) == | ||
== DNS Configuration == | == DNS Configuration == | ||
= '''DNS A record created''' pointing subdomain to VPS IP (<code>87.106.61.62</code>) = | === '''DNS A record created''' pointing subdomain to VPS IP (<code>87.106.61.62</code>) === | ||
= '''DNS propagation completed''' (can take up to 48 hours, usually much faster) = | == '''DNS propagation completed''' (can take up to 48 hours, usually much faster) == | ||
=== Verify DNS Configuration === | === Verify DNS Configuration === | ||
<pre class="lang-bash"> | <pre class="lang-bash"> | ||
= Check DNS resolution = | ==== Check DNS resolution ==== | ||
nslookup newservice.jb-vpn.uk | nslookup newservice.jb-vpn.uk | ||
= Or using dig = | == Or using dig == | ||
dig newservice.jb-vpn.uk +short | dig newservice.jb-vpn.uk +short | ||
</pre> | </pre> | ||
| Line 29: | Line 27: | ||
Before configuring the reverse proxy, verify: | Before configuring the reverse proxy, verify: | ||
= '''Service is running''' on Synology NAS = | === '''Service is running''' on Synology NAS === | ||
= '''Service is accessible''' from VPN network = | == '''Service is accessible''' from VPN network == | ||
= '''Test from VPS''': <code>curl http://10.8.0.2:[PORT]</code> ### Test Service Accessibility = | == '''Test from VPS''': <code>curl http://10.8.0.2:[PORT]</code> ### Test Service Accessibility == | ||
<pre class="lang-bash"> | <pre class="lang-bash"> | ||
= Test service from VPS = | == Test service from VPS == | ||
curl http://10.8.0.2:8080 | curl http://10.8.0.2:8080 | ||
= Check if service is listening (from Synology NAS or via SSH) = | == Check if service is listening (from Synology NAS or via SSH) == | ||
netstat -tlnp | grep PORT_NUMBER | netstat -tlnp | grep PORT_NUMBER | ||
</pre> | </pre> | ||
| Line 45: | Line 43: | ||
Ensure the following are in place: | Ensure the following are in place: | ||
= '''OpenVPN tunnel is active''' (tun0 interface up) = | === '''OpenVPN tunnel is active''' (tun0 interface up) === | ||
= '''Synology NAS is connected''' to VPN (10.8.0.2 reachable) = | == '''Synology NAS is connected''' to VPN (10.8.0.2 reachable) == | ||
= '''Nginx is running''' on the VPS = | == '''Nginx is running''' on the VPS == | ||
= '''Port 80 is accessible''' (required for SSL certificate validation) = | == '''Port 80 is accessible''' (required for SSL certificate validation) == | ||
=== Verify System Status === | === Verify System Status === | ||
<pre class="lang-bash"> | <pre class="lang-bash"> | ||
= Check VPN connectivity = | ==== Check VPN connectivity ==== | ||
ping 10.8.0.2 | ping 10.8.0.2 | ||
= Check nginx status = | == Check nginx status == | ||
systemctl status nginx | systemctl status nginx | ||
= Check VPN interface = | == Check VPN interface == | ||
ip addr show tun0 | ip addr show tun0 | ||
</pre> | </pre> | ||
Revision as of 13:44, 1 January 2026
Before adding a new service to the reverse proxy system, ensure you have the following:
Service Information
Subdomain name (e.g., newservice.jb-vpn.uk)
Internal IP address (usually 10.8.0.2 for Synology NAS)
Internal port number (e.g., 8080, 3000, etc.)
Protocol (HTTP or HTTPS)
DNS Configuration
DNS A record created pointing subdomain to VPS IP (87.106.61.62)
DNS propagation completed (can take up to 48 hours, usually much faster)
Verify DNS Configuration
==== Check DNS resolution ==== nslookup newservice.jb-vpn.uk == Or using dig == dig newservice.jb-vpn.uk +short
Service Verification
Before configuring the reverse proxy, verify:
Service is running on Synology NAS
Service is accessible from VPN network
Test from VPS: curl http://10.8.0.2:[PORT] ### Test Service Accessibility
== Test service from VPS == curl http://10.8.0.2:8080 == Check if service is listening (from Synology NAS or via SSH) == netstat -tlnp | grep PORT_NUMBER
System Requirements
Ensure the following are in place:
OpenVPN tunnel is active (tun0 interface up)
Synology NAS is connected to VPN (10.8.0.2 reachable)
Nginx is running on the VPS
Port 80 is accessible (required for SSL certificate validation)
Verify System Status
==== Check VPN connectivity ==== ping 10.8.0.2 == Check nginx status == systemctl status nginx == Check VPN interface == ip addr show tun0
Related Documentation
- [Step-by-Step Process](step-by-step.md) - Next steps after prerequisites
- [System Overview](index.md) - System architecture