We do not natively support Windows installations, as there are a number of dependencies that are only available as linux packages. If you want to install AtoM on a Windows server, we strongly
recommend using virtualization to create an Ubuntu VM to work inside, so that you can follow our recommended installation documentation
. This is mentioned in our documentation here:
If you want to take a look at some of the other threads in the user forum tagged Windows, see:
If you are just looking for a local test instance you can easily set up on a home computer (including Windows), you might want to try out our Vagrant box. The easiest instructions for installing it are found in these slides:
Please understand that this Vagrant box version of AtoM is NOT meant to be a permanent installation where you keep your data or with which run your public site - it is intended for local testing and development only!
You'll have to install Vagrant
on your computer first, and if you are a Windows user, you will also have to install PuTTY
. After that, the slides should walk you through the set up and update process.
If you want to try to proceed on a Windows server anyway, we cannot offer many suggestions. However, I would recommend that you take a look at the Requirements page
, and the Linux installation documentation
and make sure that you have installed the correct versions of all the dependencies.
The next thing I would suggest that you do is check the webserver error logs to see if you can find more useful information about the nature of the error. I don't know what webserver you are using, but you can see the default information we provide for Nginx users, here:
It's also possible that using Debug mode could tell you more about the nature of the error. See:
The most common cause I see for 500 errors is that the job scheduler is either not installed, not properly configured, or the atom-worker needs a restart. See: