chrisonline  
                (Christian Grasser)
               
                 
                 
              
                  
                    February 16, 2019,  7:11pm
                   
                   
              1 
               
             
            
              I have setup the Discourse installation on a Amazon AWS EC2 without Let’s Encrypt. 
The docker is listening on port 80 and 443 but I can’t access the site via HTTPS.
HTTP works fine but not HTTPS.
With HTTPS I get the chrome browser error “ERR_CONNECTION_REFUSED”
I have already allowed 80 and 443 withing Amazon EC2: 
I am trying to access the site at the moment via the public IP4: 
http://18.220.41.204  is working but not https://18.220.41.204 .
Can anybody help?
             
            
               
               
               
            
                
            
           
          
            
              
                Stephen  
                (Stephen)
               
              
                  
                    February 16, 2019,  7:13pm
                   
                   
              2 
               
             
            
              Https over a port without a certificate? How?
             
            
               
               
              1 Like 
            
            
           
          
            
              
                chrisonline  
                (Christian Grasser)
               
              
                  
                    February 16, 2019,  7:18pm
                   
                   
              4 
               
             
            
              So this does not work? I tought it is working but I get a warning in the browser that this site is not secure.
             
            
               
               
               
            
            
           
          
            
              
                Stephen  
                (Stephen)
               
              
                  
                    February 16, 2019,  7:19pm
                   
                   
              5 
               
             
            
              Accessing via IP isn’t supported. What certificate are you using to access over 443? Self-signed?
             
            
               
               
              3 Likes 
            
            
           
          
            
              
                chrisonline  
                (Christian Grasser)
               
              
                  
                    February 16, 2019,  7:21pm
                   
                   
              6 
               
             
            
              No certificate at the moment. 
This was only a test before I point my domain subdomain to the Amazon EC2.
I will create another thread of my main problem because I wanted to test this with Amazon EC2 
             
            
               
               
               
            
            
           
          
            
              
                pfaffman  
                (Jay Pfaffman)
               
              
                  
                    February 17, 2019, 12:34am
                   
                   
              7 
               
             
            
              Did you run discourse-setup? Did you enable let’s encrypt there?
             
            
               
               
               
            
            
           
          
            
              
                jose-zama  
                (Jose Zamudio)
               
              
                  
                    February 17, 2019,  4:52am
                   
                   
              8 
               
             
            
              
It seems you fixed it using a certificate as above link is currently responding.
             
            
               
               
              1 Like 
            
            
           
          
            
              
                chrisonline  
                (Christian Grasser)
               
              
                  
                    February 17, 2019,  6:19am
                   
                   
              9 
               
             
            
              I pointed my subdomain now to the IP and rerun the setup with SSL.
After a few hours it is now working.
             
            
               
               
               
            
            
           
          
            
              
                Stephen  
                (Stephen)
               
              
                  
                    February 17, 2019,  7:08am
                   
                   
              10 
               
             
            
              As I said earlier, IP based installs are wholly unsupported.
Let’s encrypt will work immediately, the certificate verification method is DNS.
             
            
               
               
              5 Likes