API tools faq
paste
Advertisement
Guest User

nginx

a guest
Apr 12th, 2016
114
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 14.12 KB | None | 0 0
raw download clone embed print report
  1. Setting up augeas-lenses (1.2.0-0ubuntu1.1) ...
  2. Setting up binutils (2.24-5ubuntu14) ...
  3. Setting up cpp-4.8 (4.8.4-2ubuntu1~14.04.1) ...
  4. Setting up cpp (4:4.8.2-1ubuntu6) ...
  5. Setting up dialog (1.2-20130928-1) ...
  6. Setting up libgcc-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04.1) ...
  7. Setting up gcc-4.8 (4.8.4-2ubuntu1~14.04.1) ...
  8. Setting up gcc (4:4.8.2-1ubuntu6) ...
  9. Setting up libaugeas0 (1.2.0-0ubuntu1.1) ...
  10. Setting up libpython-dev:amd64 (2.7.5-5ubuntu3) ...
  11. Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-1ubuntu1) ...
  12. Setting up libssl-dev:amd64 (1.0.1f-1ubuntu2.18) ...
  13. Setting up python2.7-dev (2.7.6-8ubuntu0.2) ...
  14. Setting up python-dev (2.7.5-5ubuntu3) ...
  15. Setting up python-pkg-resources (3.3-1ubuntu2) ...
  16. Setting up python-setuptools (3.3-1ubuntu2) ...
  17. Setting up python-virtualenv (1.11.4-1ubuntu1) ...
  18. Setting up libffi-dev:amd64 (3.1~rc1+r3.0.13-12ubuntu0.1) ...
  19. Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  20. Processing triggers for ca-certificates (20160104ubuntu0.14.04.1) ...
  21. Updating certificates in /etc/ssl/certs... 19 added, 19 removed; done.
  22. Running hooks in /etc/ca-certificates/update.d....done.
  23. Checking for new version...
  24. Creating virtual environment...
  25. Installing Python packages...
  26. Installation succeeded.
  27. Requesting root privileges to run letsencrypt...
  28. ~/.local/share/letsencrypt/bin/letsencrypt --help
  29.  
  30. letsencrypt-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
  31.  
  32. The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
  33. default, it will attempt to use a webserver both for obtaining and installing
  34. the cert. Major SUBCOMMANDS are:
  35.  
  36. (default) run Obtain & install a cert in your current webserver
  37. certonly Obtain cert, but do not install it (aka "auth")
  38. install Install a previously obtained cert in a server
  39. renew Renew previously obtained certs that are near expiry
  40. revoke Revoke a previously obtained certificate
  41. rollback Rollback server configuration changes made during install
  42. config_changes Show changes made to server config during installation
  43. plugins Display information about installed plugins
  44.  
  45. Choice of server plugins for obtaining and installing cert:
  46.  
  47. --apache Use the Apache plugin for authentication & installation
  48. --standalone Run a standalone webserver for authentication
  49. (nginx support is experimental, buggy, and not installed by default)
  50. --webroot Place files in a server's webroot folder for authentication
  51.  
  52. OR use different plugins to obtain (authenticate) the cert and then install it:
  53.  
  54. --authenticator standalone --installer apache
  55.  
  56. More detailed help:
  57.  
  58. -h, --help [topic] print this message, or detailed help on a topic;
  59. the available topics are:
  60.  
  61. all, automation, paths, security, testing, or any of the subcommands or
  62. plugins (certonly, install, nginx, apache, standalone, webroot, etc)
  63.  
  64. deciding whether to renew the cert(s)
  65. Existing certificate is still valid for another 89 day(s); skipping renewal.
  66. * Starting authentication failure monitor fail2ban
  67. ...done.
  68. Apr 12 18:59:32 15efed7044ce syslog-ng[6142]: syslog-ng starting up; version='3.5.3'
  69. Apr 12 19:00:32 15efed7044ce syslog-ng[6142]: syslog-ng shutting down; version='3.5.3'
  70. Using existing nginx.conf
  71. Using existing nginx-fpm.conf
  72. Using existing site config
  73. Using existing landing page
  74. Using existing jail.local
  75. Using existing fail2ban filters
  76. Using existing letsencrypt installation
  77. SUBDOMAINS entered, processing
  78. Sub-domains processed are: -d www.domain.ch -d plexpy.domain.ch -d headphones.domain.ch -d sonarr.domain.ch -d couchpotato.domain.ch -d nzbget.domain.ch -d cloud.domain.ch -d request.domain.ch -d esports.domain.ch
  79. Using existing DH parameters
  80. <------------------------------------------------->
  81.  
  82. <------------------------------------------------->
  83. cronjob running at Tue Apr 12 19:00:34 CEST 2016
  84. URL is domain.ch
  85. Subdomains are www,plexpy,headphones,sonarr,couchpotato,nzbget,cloud,request,esports
  86. letting the script update itself; help info may be displayed, you can ignore that :-)
  87. Checking for new version...
  88. Requesting root privileges to run letsencrypt...
  89. ~/.local/share/letsencrypt/bin/letsencrypt --help
  90.  
  91. letsencrypt-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
  92.  
  93. The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
  94. default, it will attempt to use a webserver both for obtaining and installing
  95. the cert. Major SUBCOMMANDS are:
  96.  
  97. (default) run Obtain & install a cert in your current webserver
  98. certonly Obtain cert, but do not install it (aka "auth")
  99. install Install a previously obtained cert in a server
  100. renew Renew previously obtained certs that are near expiry
  101. revoke Revoke a previously obtained certificate
  102. rollback Rollback server configuration changes made during install
  103. config_changes Show changes made to server config during installation
  104. plugins Display information about installed plugins
  105.  
  106. Choice of server plugins for obtaining and installing cert:
  107.  
  108. --apache Use the Apache plugin for authentication & installation
  109. --standalone Run a standalone webserver for authentication
  110. (nginx support is experimental, buggy, and not installed by default)
  111. --webroot Place files in a server's webroot folder for authentication
  112.  
  113. OR use different plugins to obtain (authenticate) the cert and then install it:
  114.  
  115. --authenticator standalone --installer apache
  116.  
  117. More detailed help:
  118.  
  119. -h, --help [topic] print this message, or detailed help on a topic;
  120. the available topics are:
  121.  
  122. all, automation, paths, security, testing, or any of the subcommands or
  123. plugins (certonly, install, nginx, apache, standalone, webroot, etc)
  124.  
  125. deciding whether to renew the cert(s)
  126. Existing certificate is still valid for another 89 day(s); skipping renewal.
  127. * Starting authentication failure monitor fail2ban
  128. ...done.
  129. Apr 12 19:00:35 15efed7044ce syslog-ng[131]: syslog-ng starting up; version='3.5.3'
  130. Apr 12 19:01:50 15efed7044ce syslog-ng[131]: syslog-ng shutting down; version='3.5.3'
  131. Using existing nginx.conf
  132. Using existing nginx-fpm.conf
  133. Using existing site config
  134. Using existing landing page
  135. Using existing jail.local
  136. Using existing fail2ban filters
  137. Using existing letsencrypt installation
  138. SUBDOMAINS entered, processing
  139. Sub-domains processed are: -d www.domain.ch -d plexpy.domain.ch -d headphones.domain.ch -d sonarr.domain.ch -d couchpotato.domain.ch -d nzbget.domain.ch -d cloud.domain.ch -d request.domain.ch -d esports.domain.ch
  140. Using existing DH parameters
  141. <------------------------------------------------->
  142.  
  143. <------------------------------------------------->
  144. cronjob running at Tue Apr 12 19:01:56 CEST 2016
  145. URL is domain.ch
  146. Subdomains are www,plexpy,headphones,sonarr,couchpotato,nzbget,cloud,request,esports
  147. letting the script update itself; help info may be displayed, you can ignore that :-)
  148. Checking for new version...
  149. Requesting root privileges to run letsencrypt...
  150. ~/.local/share/letsencrypt/bin/letsencrypt --help
  151.  
  152. letsencrypt-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
  153.  
  154. The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
  155. default, it will attempt to use a webserver both for obtaining and installing
  156. the cert. Major SUBCOMMANDS are:
  157.  
  158. (default) run Obtain & install a cert in your current webserver
  159. certonly Obtain cert, but do not install it (aka "auth")
  160. install Install a previously obtained cert in a server
  161. renew Renew previously obtained certs that are near expiry
  162. revoke Revoke a previously obtained certificate
  163. rollback Rollback server configuration changes made during install
  164. config_changes Show changes made to server config during installation
  165. plugins Display information about installed plugins
  166.  
  167. Choice of server plugins for obtaining and installing cert:
  168.  
  169. --apache Use the Apache plugin for authentication & installation
  170. --standalone Run a standalone webserver for authentication
  171. (nginx support is experimental, buggy, and not installed by default)
  172. --webroot Place files in a server's webroot folder for authentication
  173.  
  174. OR use different plugins to obtain (authenticate) the cert and then install it:
  175.  
  176. --authenticator standalone --installer apache
  177.  
  178. More detailed help:
  179.  
  180. -h, --help [topic] print this message, or detailed help on a topic;
  181. the available topics are:
  182.  
  183. all, automation, paths, security, testing, or any of the subcommands or
  184. plugins (certonly, install, nginx, apache, standalone, webroot, etc)
  185.  
  186. deciding whether to renew the cert(s)
  187. Existing certificate is still valid for another 89 day(s); skipping renewal.
  188. * Starting authentication failure monitor fail2ban
  189. ...done.
  190. Apr 12 19:01:57 15efed7044ce syslog-ng[131]: syslog-ng starting up; version='3.5.3'
  191. Apr 12 19:09:01 15efed7044ce /USR/SBIN/CRON[145]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
  192. Using existing nginx.conf
  193. Using existing nginx-fpm.conf
  194. Using existing site config
  195. Using existing landing page
  196. Using existing jail.local
  197. Using existing fail2ban filters
  198. Using existing letsencrypt installation
  199. SUBDOMAINS entered, processing
  200. Sub-domains processed are: -d www.domain.ch -d plexpy.domain.ch -d headphones.domain.ch -d sonarr.domain.ch -d couchpotato.domain.ch -d nzbget.domain.ch -d cloud.domain.ch -d request.domain.ch -d esports.domain.ch
  201. Using existing DH parameters
  202. <------------------------------------------------->
  203.  
  204. <------------------------------------------------->
  205. cronjob running at Tue Apr 12 19:09:50 CEST 2016
  206. URL is domain.ch
  207. Subdomains are www,plexpy,headphones,sonarr,couchpotato,nzbget,cloud,request,esports
  208. letting the script update itself; help info may be displayed, you can ignore that :-)
  209. Checking for new version...
  210. Requesting root privileges to run letsencrypt...
  211. ~/.local/share/letsencrypt/bin/letsencrypt --help
  212.  
  213. letsencrypt-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
  214.  
  215. The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
  216. default, it will attempt to use a webserver both for obtaining and installing
  217. the cert. Major SUBCOMMANDS are:
  218.  
  219. (default) run Obtain & install a cert in your current webserver
  220. certonly Obtain cert, but do not install it (aka "auth")
  221. install Install a previously obtained cert in a server
  222. renew Renew previously obtained certs that are near expiry
  223. revoke Revoke a previously obtained certificate
  224. rollback Rollback server configuration changes made during install
  225. config_changes Show changes made to server config during installation
  226. plugins Display information about installed plugins
  227.  
  228. Choice of server plugins for obtaining and installing cert:
  229.  
  230. --apache Use the Apache plugin for authentication & installation
  231. --standalone Run a standalone webserver for authentication
  232. (nginx support is experimental, buggy, and not installed by default)
  233. --webroot Place files in a server's webroot folder for authentication
  234.  
  235. OR use different plugins to obtain (authenticate) the cert and then install it:
  236.  
  237. --authenticator standalone --installer apache
  238.  
  239. More detailed help:
  240.  
  241. -h, --help [topic] print this message, or detailed help on a topic;
  242. the available topics are:
  243.  
  244. all, automation, paths, security, testing, or any of the subcommands or
  245. plugins (certonly, install, nginx, apache, standalone, webroot, etc)
  246.  
  247. deciding whether to renew the cert(s)
  248. Existing certificate is still valid for another 89 day(s); skipping renewal.
  249. * Starting authentication failure monitor fail2ban
  250. ...done.
  251. Apr 12 19:09:51 15efed7044ce syslog-ng[135]: syslog-ng starting up; version='3.5.3'
  252. Apr 12 19:10:32 15efed7044ce syslog-ng[135]: syslog-ng shutting down; version='3.5.3'
  253. Using existing nginx.conf
  254. Using existing nginx-fpm.conf
  255. Using existing site config
  256. Using existing landing page
  257. Using existing jail.local
  258. Using existing fail2ban filters
  259. Using existing letsencrypt installation
  260. SUBDOMAINS entered, processing
  261. Sub-domains processed are: -d www.domain.ch -d plexpy.domain.ch -d headphones.domain.ch -d sonarr.domain.ch -d couchpotato.domain.ch -d nzbget.domain.ch -d cloud.domain.ch -d request.domain.ch -d esports.domain.ch
  262. Using existing DH parameters
  263. <------------------------------------------------->
  264.  
  265. <------------------------------------------------->
  266. cronjob running at Tue Apr 12 19:10:36 CEST 2016
  267. URL is domain.ch
  268. Subdomains are www,plexpy,headphones,sonarr,couchpotato,nzbget,cloud,request,esports
  269. letting the script update itself; help info may be displayed, you can ignore that :-)
  270. Checking for new version...
  271. Requesting root privileges to run letsencrypt...
  272. ~/.local/share/letsencrypt/bin/letsencrypt --help
  273.  
  274. letsencrypt-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
  275.  
  276. The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
  277. default, it will attempt to use a webserver both for obtaining and installing
  278. the cert. Major SUBCOMMANDS are:
  279.  
  280. (default) run Obtain & install a cert in your current webserver
  281. certonly Obtain cert, but do not install it (aka "auth")
  282. install Install a previously obtained cert in a server
  283. renew Renew previously obtained certs that are near expiry
  284. revoke Revoke a previously obtained certificate
  285. rollback Rollback server configuration changes made during install
  286. config_changes Show changes made to server config during installation
  287. plugins Display information about installed plugins
  288.  
  289. Choice of server plugins for obtaining and installing cert:
  290.  
  291. --apache Use the Apache plugin for authentication & installation
  292. --standalone Run a standalone webserver for authentication
  293. (nginx support is experimental, buggy, and not installed by default)
  294. --webroot Place files in a server's webroot folder for authentication
  295.  
  296. OR use different plugins to obtain (authenticate) the cert and then install it:
  297.  
  298. --authenticator standalone --installer apache
  299.  
  300. More detailed help:
  301.  
  302. -h, --help [topic] print this message, or detailed help on a topic;
  303. the available topics are:
  304.  
  305. all, automation, paths, security, testing, or any of the subcommands or
  306. plugins (certonly, install, nginx, apache, standalone, webroot, etc)
  307.  
  308. deciding whether to renew the cert(s)
  309. Existing certificate is still valid for another 89 day(s); skipping renewal.
  310. * Starting authentication failure monitor fail2ban
  311. ...done.
  312. Apr 12 19:10:37 15efed7044ce syslog-ng[136]: syslog-ng starting up; version='3.5.3'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!