Is SSL supported in proxy options ?

[Neijin]

First, thank you and all the contributors for your work. Is SSL support planned for mup-node ? And what about the volume option ?

[zodern]

All of the proxy options should work with mup-node.

For volumes, you can use app.docker.args. I might add the volume option in the future.

[Neijin]

I'll test that and I'll get back to you.

[Neijin]

@zodern I'm still not able to get SSL working on a simple Node project. When the "proxy" option is removed, everything works fine.

This is my mup.js file :

module.exports = {
servers:
{
one:
{
host: 'XX.XX.XX.XX',
username: 'admin',
pem: 'id_rsa_o'
}
},
app:
{
name: 'app-name',
path: '../',
type: 'node',
nodeVersion: '8.8.1',
servers:
{
one: {},
},
env:
{
NODE_ENV: 'production'
},
startScript: 'start',
docker:
{
buildInstructions:
[
'RUN apt-get -y update'
]
}
},
proxy:
{
domains: 'mydomain.com,www.mydomain.com',
ssl:
{
letsEncryptEmail: 'contact@myotherdomain.com',
forceSSL: true
}
},
plugins: [ 'mup-node' ]
};

When executing mup setup then mup deploy --verbose everything seems fine and the deployment of the app is a success. Both mydomain.com & www.mydomain.com redirect to my server (tested without the proxy option).

Unfortunately, when executing mup status I have the following results :

=> Servers

• XX.XX.XX.XX: Debian 9.7
  => Docker Status
• XX.XX.XX.XX: 18.09.1 Running
  => Reverse Proxy Status
• XX.XX.XX.XX:
  • NGINX:
    • Status: Stopped
  • Let's Encrypt
    • Status: Stopped

So it seems like the reverse proxy is not working, explaining why I cannot connect to my server with the "proxy" option.

[Neijin]

After further investigations :

• mup proxy nginx-config is empty after deployment
• mup proxy start throws the error :

[51.77.148.169] x Start proxy: FAILED
------------------------------------STDERR------------------------------------
bash: line 6: cd: /opt/mup-nginx-proxy: No such file or directory
------------------------------------STDOUT------------------------------------

[Neijin]

Got it working !

You need to execute mup proxy setup after running mup setup and mup deploy.
The NGINX configuration is then generated and the reverse proxy starts without errors.

[joaocarloscabral]

Hello!

I'm having trouble configuring access via https.

I did all configurations as descibred.

module.exports = {
  servers: {
    one: {
      host: 'xxx',
      username: 'ubuntu',
      pem: '~/.ssh/ssh-root.pem'
    }
  },

  proxy: {
    domains: 'sub.domain.com.br',
    ssl: {
      forceSSL: true,
      letsEncryptEmail: 'contact@domain.com.br'
    },
  },


  app: {
    // TODO: change app name and path
    name: 'app',
    path: '../..',
    type: 'node',
    nodeVersion: '8.10',

    servers: {
      one: {},
    },

    startScript: 'start:production',
    
    docker: {
      args: ['--network=host'],
    },

    env: {
      MONGO_URI: 'xxxx',
    },
  },

  plugins: [ 'mup-node' ]

};

by mup proxy logs-le i can see that the certificates was generated correctly.

2020-07-24 17:24:28,514:INFO:simp_le:1581: Certificates already exist and renewal is not necessary, exiting with status code 1.

But my app is acessible just by port 3000 without https protocol.

@zodern do you have some tips to help?

Thanks!

[zodern]

@joaocarloscabral it has to be on the same network as the proxy (bridge network) to work. You would load it from ports 80 or 443 (the default ports for http and https).

[joaocarloscabral]

Wow!

Sorry, I didn't see that little detail.

Worked like a charm. Thanks a lot!!