Question

HTTP Error 500 preventing access to website

Hi! I currently work as an archivist for a nonprofit museum and this week I have been unable to access our digital archive website which was configured using Collective Access. Basically both the front-end (pawtucket) and back-end (providence) are inaccessible and show up as blank screens. The front end gave me an error code HTTP Error 500 which I assume has something to do with the server but I’m clueless on the steps I need to take to fix the issue. Would definitely appreciate any help or direction!


Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

KFSys
Site Moderator
Site Moderator badge
January 20, 2023

Heya @brianaflanagan,

The blank screen would mean there is somekind of an error with the website’s code or configuration. It should be easy to fix. First you need to SSH to your Droplet.

You can use the DigitalOcean Web Console:

https://docs.digitalocean.com/products/droplets/how-to/connect-with-console/

Once inside, you can go to your /var/log folder, open your website to generate the error once again in the logs and check their last entries.

Bobby Iliev
Site Moderator
Site Moderator badge
January 19, 2023

Hi there,

What I could suggest is to first try and access your server so you could then go from there and check your server logs for more information on what might be causing that 500 error:

https://docs.digitalocean.com/products/droplets/how-to/connect-with-ssh/

If you are unable to access your server via SSH, I would recommend following the steps here on how to recover your access:

https://docs.digitalocean.com/support/i-lost-the-ssh-key-for-my-droplet/

Once you have access to your server I would recommend checking your logs to see what the actual problem is rather than the generic 500 error.

Feel free to share the output of your logs here as well so we could advise you further!

Best,

Bobby