[[TracNav(doc/RPKI/TOC)]] [[PageOutline]] = Apache Configuration = This page documents how to configure Apache to server the web portal application. During the software install process, `/usr/local/etc/rpki/apache.conf` is created, which needs to be included from the apache configuration inside of a `VirtualHost` section. Note that the web portal application '''requires TLS''' to be enabled for the `VirtualHost` it is configured in, otherwise it will fail to operate. == Requirements == * Apache 2.2 or later * mod_ssl * mod_wsgi 3 or later == Debian & Ubuntu == First, you need to install `apache` and enable SSL. Run the following commands in a shell as '''root''': {{{#!sh apt-get install apache2 libapache2-mod-wsgi a2enmod ssl a2ensite default-ssl }}} Edit `/etc/apache2/sites-enabled/default-ssl` and place the following line inside the `` section: {{{ Include /usr/local/etc/rpki/apache.conf }}} Now restart `apache`: {{{#!sh service apache2 restart }}} == FreeBSD == Now configure apache, using `/usr/local/etc/rpki/apache.conf`, e.g. {{{ #!sh $ cp apache.conf /usr/local/etc/apache22/Includes/rpki.conf }}} Restart apache {{{ #!sh $ apachectl restart }}} == Running the web portal as a different user (optional) == By default, the web portal is run in embedded mode in mod_wsgi, which means it runs inside the apache process. However, you can make the web portal run in daemon mode as a different user using mod_wsgi. {{{ #!sh $ ./configure --enable-wsgi-daemon-mode[=user[:group]] }}} Where `user` is the optional user to run the web portal as, and `group` is the optional group to run the web portal as. If `user` is not specified, it will run in a separate process but the same user as apache is configured to run. Note that when run in daemon mode, a unix domain socket will be created in the same directory as the apache log files. If the user you have specified to run the web portal as does not have permission to read a file in that directory, the web interface will return a **500 Internal Server Error** and you will see a **permission denied** error in your apache logs. The solution to this is to use the `WSGISocketPrefix` apache configuration directive to specify an alternative location, such as: {{{ WSGISocketPrefix /var/run/wsgi }}} Note that this directive **must not** be placed inside of the `VirtualHost` section. It **must** be located at the global scope. see http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGISocketPrefix for more information. == Verify the Web Portal is Working == Navigate to https://YOURHOST/rpki/ and you should see the login page for the web portal. Enter the superuser and password in login form (see [[wiki:doc/RPKI/CA/UI/GUI/UserModel]] if you haven't yet created a superuser). If you've only done the above bootstrap, there will only be a single handle to manage, so the GUI will automatically bring you to the dashboard for that handle.:26:01 +0000 committer Rob Austein <sra@hactrn.net> 2007-11-12 20:26:01 +0000 More notes on CRL and revocation' href='/sra/rpki.net/commit/scripts/README?h=zone-cleanup&id=8fff9fbcbc986dcaa706831592f26f84e40d8a00'>8fff9fbc

7
8

12
13

14
15

21
22

59
60

62
63
64

101
102
103

123
124

142
143

150
151

162
163
164

183
184
185

199
200
201

235
236

240
241

250
251

255
256

258
259
260

277
278

283
284
285

286
287
288

326
327
328

329
330

341
342

344
345

352
353

355
356

358
359
360

365
366
367