XF 2.1 Testing new target site before transfer

[Tom McIntyre]

I am struggling to get my XF2.1 site going on a Digital Ocean droplet under centminmod.

I have nominally done a successful install. All the files are owned by nginx:nginx but I changed the permissions on data and internal_data to 0777.

My big stumbling block at the moment is that I am being blocked by my license not matching my URL in the admincp. I thought I could do testing on this site so long as it was not open to the public without needing an additional license. I cannot install any of the addons with this condition in place.

I also get the message which may be a side effect to the basic license problem when I try to log in to the front end with my admin account.

Is there a simple fix for this?

 

[Tom McIntyre]

Since this is a basic site, I decided to just re-install. That seems to have fixed my problems.

However, if I try to use https to connect to the site, I get page not found. I thought that https was the default for new installations.

 

[Max Taxable]

I thought that https was the default for new installations.

You have an SSL certificate installed for the domain?

 

[Tom McIntyre]

I thought it was the default with centminmod on Digital Ocean, but I am probably wrong as the evidence suggests.

 

[Lukas W.]

I thought it was the default with centminmod on Digital Ocean, but I am probably wrong as the evidence suggests.

SSL certs can't be shipped per default as they need to be tailored individually for your server and registered by an external server. You can use certbot to easily manage a LetsEncrypt cert.

 

[Tom McIntyre]

I tried to follow the instructions on the Centminmod discussion site, but I think I misunderstood.

Since the domain already existed, on the host, I tried to pick up the process at the second step. I found it a little difficult to enter the 300 or so character string to install the cert, but in the end, it did not accept the name of my domain. i.e. it said the domain did not exist.

I will spend a little more time on it later today. I am starting to remember some of the things I learned about bourne Shell 30 years ago.

 

[Itworx4me]

I tried to follow the instructions on the Centminmod discussion site, but I think I misunderstood.

Since the domain already existed, on the host, I tried to pick up the process at the second step. I found it a little difficult to enter the 300 or so character string to install the cert, but in the end, it did not accept the name of my domain. i.e. it said the domain did not exist.

I will spend a little more time on it later today. I am starting to remember some of the things I learned about bourne Shell 30 years ago.

https://centminmod.com/migrating-to-https.html

 

[Tom McIntyre]

https://centminmod.com/migrating-to-https.html

Yes, that was what I was using but starting at step 2 since the domain already existed on the host. I suspect I am confused by vhost vs host when trying to generate a cert.

I tried it a second time from the top, but it did not use the existing a record for the subdomain so it ended up with two different ip addresses and refused to continue. It is possible that it does not work the same since my subdomain testmb.nawcc.org has an a record of its own. The process seems to have selected an ip address for the vhost that is related to the nawcc.org isp address. The process may try to do something with the parent domain.

Maybe when everyone is back to work tomorrow I will be able to get it sorted out.