Hi!
I have been researching and trying out many different ways to kill my non resolve issues I’m so stuck I can’t but ask if any experienced user can see the issue.
Domain Registrar: GoDaddy. My normal home web-page’s domain is mydomain.com which forwards to an instapage website, but I want a subdomain login.mydomain.com to redirect (301) to my DO droplet. I added subdomain masked forwarding (HTTP) to my DO IP address, added the three nameservers for login.mydomain.com in GoDaddy, and added an A record for login that points to the DO IP address.
Deploying Meteor I follow the this guide https://www.digitalocean.com/community/tutorials/how-to-deploy-a-meteor-js-application-on-ubuntu-14-04-with-nginx My /etc/nginx/sites-available/myapp.conf file:
server_tokens off;
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
server {
listen 80 default_server;
listen [::]:80 default_server ipv6only=on;
root /usr/share/nginx/html; # root is irrelevant
index index.html index.htm; # this is also irrelevant
server_name login.mydomain.com;
location / {
rewrite ^ https://$server_name$request_uri? permanent;
}
}
server {
listen 443 ssl spdy;
server_name login.mydomain.com;
root html;
index index.html;
ssl_certificate /etc/nginx/ssl/server.pem;
ssl_certificate_key /etc/nginx/ssl/server.key;
ssl_stapling on;
ssl_session_cache shared:SSL:10m;
ssl_session_timeout 5m;
ssl_prefer_server_ciphers on;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:ECDHE-RSA-RC4-SHA:ECDHE-ECDSA-RC4-SHA:RC4-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK';
add_header Strict-Transport-Security "max-age=31536000;";
if ($http_user_agent ~ "MSIE" ) {
return 303 https://browser-update.org/update.html;
}
location / {
proxy_pass http://127.0.0.1:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade; # allow websockets
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Forwarded-For $remote_addr; # preserve client IP
if ($uri != '/') {
expires 30d;
}
}
}
My /etc/init/myapp.conf:
description "Meteor.js (NodeJS) application"
author "Daniel Speichert <daniel@speichert.pro>"
start on started mongodb and runlevel [2345]
stop on shutdown
respawn
respawn limit 10 5
setuid myapp
setgid myapp
script
export PATH=/opt/local/bin:/opt/local/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript
export PWD=/home/myapp
export HOME=/home/myapp
export BIND_IP=127.0.0.1
export PORT=8080
export HTTP_FORWARDED_COUNT=1
export MONGO_URL=mongodb://localhost:27017/myapp
export ROOT_URL=https://login.mydomain.com
exec node /home/myapp/bundle/main.js >> /home/myapp/myapp.log
end script
NOTES
Does anyone know why it does not resolve? I can ping the DO droplet’s IP address, but when I do a GET request with chrome it does not resolve (107.170.70.47:80)
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.
This question is irrelevant, it turned out to be a persistent 502 Bad Gateway error. See here: https://www.digitalocean.com/community/questions/502-bad-gateway-remains-meteor-js-nginx
Name resolution is unrelated to your server configuration and you decided to censor the domain name, so nothing can be done to help.
What is the domain?