Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.

If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping

Answers may be delayed for posts that do not include sufficient information.

Login screen not found for providence.

I have worked through the Providence install instructions, and ran the installer using a template (castle_0.xml).
All directories and the nginx user are www-data:www-data.

I receive the screen saying installation is complete, and that I can now login.
But when I click on the word "login", it takes me to a page with the 404 Not found error.
From the nginx error log:
*377 directory index of "/var/www/html/providence/app/" is forbidden, client:, server:, request: "GET /app/ HTTP/1.1", host: ""

The app directory is owned by www-data and has drwxr-xr-x permissions.

A "Hello World" index.html file in the providence directory displays correctly (

How can I proceed?


  • I should have added:
    Ubuntu Server 18.04
    Providence 1.7

    Pawtucket not yet installed.

  • You might have already thought of this fact, but did you set up nginx to point to /var/www/html/* in the configuration file for the site? When I was trying out nginx as an alternative, the default configuration of nginx pointed to /usr/share/nginx/html/* so perhaps the problem is due to the server looking for the files in the wrong place.

  • Good thought, but I did have the correct path in nginx conf file.
    I progressed a little with installation, currently working on file permissions.

  • The problem was that I was using nginx for one site, and apache2 for this one. I did not have the configuration correct, and rewrites were not working. I have removed nginx, and everything is fine.

Sign In or Register to comment.