Skip to content

Moving servers - verifying that Sendy works?

edited November 2018 in Questions

We are moving our website (and Sendy) to a new server and I want to make sure everything is working before going live on it.

Is there a way to test that Sendy transitioned successfully without having to actually change DNS?

Thanks in advance.

(I tried but couldn't find anything that quite matched my question using the search function. )

Comments

  • BenBen
    edited November 2018

    Hi,

    You can check this list of steps against what you've done on migrating Sendy to a new server → https://sendy.co/forum/discussion/4710/how-to-migrate-sendy-to-another-server#Item_2

    Thanks.

    Best regards,
    Ben

  • edited November 2018

    Ben,

    I did see that thread and have already done/attempted most of steps 1 through 3 but there are a couple of parts I'm not sure about.

    Steps 1 and 2 have been completed. (And correctly I believe.)

    Step 3 - What do I use for 'APP_PATH' and/or possibly $dbHost in the new server's Config file? Since our domain is still pointing at our old/current server, the only way to access the site on the new server is via the new server's IP address.

    In step 4 - How does the above play in to using 'http://sendy.co/#forms'? We don't want to lose the ability to use Sendy on the current server before we are ready to move to the new server.

    Along with the above, trying to access the Sendy installation at the new installation currently shows just the header at the top with no User/PW boxes. I've tried using the IP address in a couple of different configurations but have had no luck in getting the login page to work.

    Step 5 - Thought I'd deal with this once I actually have Sendy accessible on the new server.

    Step 6 - Already double checked that the chron job was in place.

    Looking forward to additional guidance. On a side note, I've just submitted a separate ticket on issues I'm having after upgrading Sendy on our current (live) server.

    Thanks,

    Dave

  • BenBen
    edited November 2018

    Hi,

    What do I use for 'APP_PATH' and/or possibly $dbHost in the new server's Config file?

    Map an A record that points test.yourdomain.com to 123.4.5.6.7 (the IP address) so that you can access the new installation at https://test.yourdomain.com/~f0odb1zj/Outbound/' without having any licensing errors while testing

    The reason why you're getting a blank page with only a header on top is because your server does not have gettext extension installed on the server:

    Best regards,
    Ben

  • TERRIFIC Ben!

    Your directions got me up and running on the new server. We are hoping to be fully transfered over to this new server within the next couple of weeks. In the mean time we will use this new set up until the issue on our current server is resolved.

    Thanks!

    Dave

This discussion has been closed.