How To Set Up CMS on SubDomain on a 2nd Server

DISREGARD - I just needed to set up my SSL :-/

I would like to set up a sub-domain “”, on a second server, for my CMS. The IP address for the sub-domain’s server works, but the URL just times out. I believe its a problem with my nginx server blocks but I’m not positive.

I set up an A record on the DNS for to point to the subdomain on the 2nd server. I do currently have a working subdomain for my Hike SEO portal that points to their app, “” with an A record recorded on the DNS for

Here’s the nginx Server block for, with replacement text for the IPs and domains:

server {
        listen SERVER1_IP:443 ssl http2;
        listen [::]:443 ssl http2 ipv6only=on;
        ssl_certificate /etc/letsencrypt/live/;
        ssl_certificate_key /etc/letsencrypt/live/;
        include /etc/letsencrypt/options-ssl-nginx.conf;
	ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

        ssl_stapling on;
        ssl_stapling_verify on;

        root /var/www/;
        index index.html index.html index.nginx-debian.html;


        location / {
                proxy_pass 'http://localhost:3000';
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection 'upgrade';
                proxy_set_header Host $host;
                proxy_cache_bypass $http_upgrade;

	expires $expires;
server {
        if ($host = {
                return 301 https://$host$request_uri;

        listen SERVER1_IP:80;
        listen [::]:80;

        return 301 https://$server_name$request_uri;
server {
        listen SERVER1_IP:80;
        listen SERVER1_IP:443;


	location / {
		return 301$request_uri;

And here’s the server block for–(Note, I have not yet set up SSL on the subdomain)

server {
	listen SERVER2_IP:80;
	root /var/www/cms;
	index index.html index.htm;

	location / {
		try_files $uri $uri/ =404;

	location ~ \.php$ {
		include snippets/fastcgi-php.conf;
		fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;

	location ~/\.ht {
		deny all;

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Site Moderator
Site Moderator badge
May 31, 2023

Hey @danielbranda,

Basically, if you were accessing the subdomain at then yes you needed a nginx config file for port 443 with an SSL.

Having said that you should’ve been posible to open the website with http -

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel