1. background
2. step 1: sign up under the new system
3. step 2: upload your website
1. static websites
2. dynamic website
4. step 3: change DNS

Migration Notes

If you currently have a website hosted by riseup.net, but you have not yet transferred it over to the new server, than this page is for you!

background

Our new hosting server (raven.riseup.net) has many more features, has more capacity, and is much more secure.

The old hosting server (crow.riseup.net) is very sick: it is very insecure, the hardware is failing, and backups are no longer being made. The sooner you can move your site the better.

Once you are registered with the new system, you will be able to create email accounts/aliases/forwards, create and access your database, and view traffic reports all from a handy control panel. Also, you automatically get the domain username.revolt.org (where username is the name you choose for the login to administer your site).

However, we will no longer allow sites in the form riseup.net/path. We are doing this to improve security, reduce our legal liability, and because it would be very difficult to support this on the new system.

step 1: sign up under the new system

Go to help.riseup.net and use the helpdesk support form to fill out a request for hosting.

step 2: upload your website

You will automatically be assigned a username.revolt.org domain. You can use this domain to test out your site before you move your custom domain, or you can just start using the revolt.org domain as well.

static websites

If your website is static, simply copy over the html files to the new server. We only accept ssh and sftp connections on the new server.

login information:

For example, if your hosting username was smashthestate, you would sftp to smashthestate.revolt.org using the login smashthestate.

dynamic website

On the new system, we are installing and maintaining several popular Content Management Systems, bamboo, drupal, pmwiki and we plan to host wordpress soon. If you want a site using any of these, all you have to do is request it.

However, we will no longer allow you to install your own web applications. We are doing this because many people are running code which is out of date, buggy, insecure, no longer maintained, and is a total pain for us. Old code on the current system has been exploited by people attacking the server and by spammers. So, we are going to maintain, upgrade, and patch the code which is installed on the server--so you don't have to and so it stays secure.

If you need help, we will assist you in migrating to one of our supported content management systems.

step 3: change DNS

note: you only need to do this if you have a custom domain.

If you are using riseup.net's DNS server, you will need to change which nameserver your domain uses. Previously, to use riseup.net for DNS, you would set the primary nameserver to be ns1.riseup.net and the secondary to fs.freespeech.org (you do this through the website of your domain registrar). You will need to change the nameservers to these new values:

Do not make this change in your domain registration until you have moved your site to the new server. Your domain must have been added to syscp at least one hour prior to changing the nameservers with the registrar.

If your domain does not use riseup.net for DNS hosting, then you need to set this values in your domain: