Changes between Version 7 and Version 8 of ipmi
- Timestamp:
- Jun 28, 2019, 3:26:11 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ipmi
v7 v8 52 52 == Enable http redirections == 53 53 54 On robideau, we have the following nginx configuration to allow web-based proxying:54 On robideau, we have the following nginx configuration name <server>.conf to allow lets encrypt to find and validate https certificates: 55 55 56 56 {{{ 57 #server { 58 # listen 80; 59 # server_name ipmi.john.mayfirst.org; 60 # root /var/www/html; 61 # location /.well-known/acme-challenge { 62 # try_files $uri $uri/ =404; 63 # } 64 # location / { 65 # return 301 https://$host$request_uri; 66 # } 67 #} 57 server { 58 listen 80; 59 server_name ipmi.john.mayfirst.org; 60 root /var/www/html; 61 location /.well-known/acme-challenge { 62 try_files $uri $uri/ =404; 63 } 64 location / { 65 return 301 https://$host$request_uri; 66 } 67 } 68 }}} 68 69 70 In addition, we have this <server.ssl.conf version to actually proxy to the IPMI server: 71 72 {{{ 69 73 server { 70 74 listen 443; … … 95 99 ssl_dhparam /etc/ssl/dhparam.pem; 96 100 97 add_header Strict-Transport-Security max-age=63072000; 101 # Don't use strict transport or it may mess up lets encrypt. 102 #add_header Strict-Transport-Security max-age=63072000; 98 103 add_header X-Content-Type-Options nosniff; 99 104 } 100 105 }}} 101 106 102 The commented out section must be un-commented initially to allow lets encrypt to create a proper initial certificate.107 The ssl section must be disable initially until lets encrypt can be run to generate the cert. 103 108 104 109 Also, you need to create dlparams with: … … 109 114 110 115 And, of course, you need to create a DNS record so that a domain (e.g. `ipmi.john.mayfirst.org`) points to robideau's IP address. 111 112 113 116 114 117 == So-called Serial access == … … 144 147 == Disable web config == 145 148 146 Once you have working serial access, be sure to turn off nginx on robideau. We don't need to leave that open to the world. But it's handy to have in case you want to restart the physical server or something goes wrong with console access.149 Once you have working serial access, be sure to delete the link to the <server>.ssl.conf file in site-enabled so it is no accessible (but keep the <server>.conf file so letsencrypt can do it's job.