Not sure why everyone opens a new thread but to keep it compact I renamed the thread title.
Here are two other users that seem to have a similar issue from different versions to 4.0.10
and
anyone else?
Not sure why everyone opens a new thread but to keep it compact I renamed the thread title.
Here are two other users that seem to have a similar issue from different versions to 4.0.10
and
anyone else?
Seems to be the same error/cause than Upgrade Issue, SSL-Renewal error 4.0.x -> 4.0.10
Cross linking to collect this stuff within one thread: Upgrade Issue, SSL-Renewal error 4.0.x -> 4.0.10
How do I totally remove ee v4 as I want to install ee v3 instead. The reason is because I can’t make ee v4 working in local dev server with local domain like myproject.local.
Thanks.
sudo rm -fr /*.*
but don’t do that… I’m pretty sure it’s not removable. just rebuilt a fresh machine.
Ok how can i do it? As i can see i am running into 2problems
If i give admin the permissions, i get error on wordpress uploads, but i if i give permissions to www-data, the root is not able to write any files onto server.
Please let me know how to do it.
Hello,
I need non-www (naked domain) to forward to www. So domain.com to www.domain.com. I ran the below command using a sudo user:
sudo ee site create www.domain.com --type=wp --ssl=le --wildcard
I added the txt records and ran sudo ee site ssl www.domain.com once the records propagated. The SSL successfully installed. When I visit domain.com I get an SSL error but when I visit www.domain.com everything works great.
I have tried multiple times and when creating the site using www, the non-www doesn’t forward. Any suggestions?
Hello,
I need non-www (naked domain) to forward to www. So domain.com to www.domain.com. I ran the below command using a sudo user:
sudo ee site create www.domain.com --type=wp --ssl=le --wildcard
I added the txt records and ran sudo ee site ssl www.domain.com once the records propagated. The SSL successfully installed. When I visit domain.com I get an SSL error but when I visit www.domain.com everything works great.
I have tried multiple times and when creating the site using www, the non-www doesn’t forward.
When I run:
I get:
-rw-r–r-- 1 root root 3665 Mar 5 16:43 default.conf
-rw-r–r-- 1 root root 780 Mar 5 16:42 www.domain.com-redirect.conf
When I run:
ee cli info
±------------------±---------------------------------------------------------------------------+
| OS | Linux 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 |
| Shell | /bin/bash |
| PHP binary | /usr/bin/php7.2 |
| PHP version | 7.2.15-1+ubuntu18.04.1+deb.sury.org+1 |
| php.ini used | /etc/php/7.2/cli/php.ini |
| EE root dir | phar://ee.phar |
| EE vendor dir | phar://ee.phar/vendor |
| EE phar path | /root |
| EE packages dir | |
| EE global config | /opt/easyengine/config/config.yml |
| EE project config | |
| EE version | 4.0.10 |
±------------------±---------------------------------------------------------------------------+
Any suggestions?
Thank you
Hello,
After some digging and testing most of the day I discovered that if you set up EE or create the website with a sudo user, the redirect wont work. You have to create it using root. You also need to have a sudo user created or you cant update or download any plugins.
So for the redirect to work and WP to be able to install/update plugins and themes you need to make sure you have a sudo user setup. Then you need to use root to setup EE and WP.
It does work but it is not the best way to run. Hopefully a update is rolled out soon so that many of these bugs are fixed. I feel like many users are abandoning EE and using other tools.
Any updates in the pipeline?
Thank you
Here’s what you need to do:
user mod -aG www-data user
sudo chmod -R g+w /path/to/htdocs
You should be able to upload and edit files now.
I’ll take a look. Thanks for the heads up.
By the way, before I moved back to Scotland I lived 35 years in St Ives near Ringborne and think the stretch of coast along the Purbecks is some of the nicest in the country.
If Webinoly turns out to be at least half as nice, I’ve found a watch.
One of the easiest options is using Updraft Plugin, they have a migration part where a backup is taken of the site you want to migrate and then pushes all the stuff to the new site, changing URL’s and everything. You can also just take a backup in zip format, upload it to the new server in Updraft folder and then restore the new site from that. For more advanced workflows, I think Bedrock and Trellis are better though.
Thanks all. I ended up rebuilding the machine because ee v3 doesn’t support Debian 9 which was the OS on the existing machine.
I have certainly done my fair share of rsync and wp db export|import command line wrangling. About a year ago I found a commercial plugin called WP MIGRATE PRO and it worked great. It does a fantastic job of allowing one to sync databases between different environments with a simple push/pull nomenclature, it handles the renaming of links in the db and it handles the synching of the uploads directory. I have used this plugin on both easyengine sites as well as Trellis/Bedrock sites. What I failed to realize until about a month ago is that there is a GPL port of that plugin on Github. Now you can get this great plugin minus the $100 costs. Go to the Github page and check out their description and videos.
*NB I have no affiliation with the plugin or the commercial version WP Migrate Pro outside of being a super happy user. I realize that for the command line junkies in the forums this may be a slap in the face to use a plugin. But when it comes time to pass off projects to customers, a plugin like this one assures that you at least have a fighting change to get the customer to continue to utilize a staging-production workflow.
Update on that one: I’ve worked with one of the team members to fix this issue. They have fixed it in the current nightly build and a new minor version should be out very soon that fixes the issue.
Thanks to @mrrobot47 for working that out!
need help . getting error when creating site with --ssl=le at digitalocean .
Starting SSL verification.
Warning: Server error: GET http://findtopreview.com/.well-known/acme-challenge/QUD-w1lGGGffyMlABJF8zPGo7jM4i8eCdVyPF2YokTk
resulted in a 521 Origin Down
response:
Starting SSL verification.
Warning: Server error: GET http://findtopreview.com/.well-known/acme-challenge/QUD-w1lGGGffyMlABJF8zPGo7jM4i8eCdVyPF2YokTk
resulted in a 521 Origin Down
response:
ok , i did it myself . just added . cloudflare ips to digitalocean firewall.
I am trying to import sql database but getting this error.
This file is exported from ee v3 and same is not getting imported in ee v4
Have increased max_execution_time to 300 but still no success.