First, THANK YOU SO MUCH FOR THIS TOOL!
Hi I have two questions. I'm in the process of migrating a subdomain multisite that was made before 3.5 and it's domain is setup as aaa.example.org with other sites like bbb.example.org. I mention this because it's not a typical example.org with other subdomains in front of it.
I really appreciate your quick answer. Sorry if it seemed like I didn't read the documentation. I did my best to search the documentation as well as this forum before I submitted the question. I apologize for my confusion in regards to multisite compatibility.
So with your assurance, I tried the normal documented way of applying the wildcard cert (sudo site aaa.example.org -ssl=on -wildcard). However, with my multisite the main wordpress site is a subdomain (ex aaa.example.org) so when I tried to add the ssl wildcard it made it for *.aaa.example.org. Do you have any advice? I was able to generate a manual certbot cert for *.example.org but I'm not sure there is a simple webinoly way of attaching it to my site. I appreciate any advice you could give.
As for the fastcgi, testing by using 'curl -I example.org' didn't seem to show me that fastcgi was running on my multisite. Would you recommend another test?
(Since I've found so much value in the forums I want to document the steps so others can maybe find this helpful)
Thanks, in regards to the ssl, I used the manually requested wildcard cert (
sudo certbot certonly --manual --preferred-challenges=dns --manual-public-ip-logging-ok -d example.org -d *.example.org --email firstname.lastname@example.org --no-eff-email --agree-tos --staple-ocsp --must-staple
and edited the /etc/nginx/sites-enabled/aaa.example.org to point to the manually requested ssl cert files.
As for Fast-cgi
I have fast-cgi working but now I need to troubleshoot why it's not purging after an update. I have to manually hit purge page after an update. I've looked at nginx helper's logs and it looks like nginx is starting the purge on page updates correctly but doesn't completely finish. It gets to the line
2020-03-18 13:43:41 | INFO | Function purge_post END ^^^
But unless I manually purge, it doesn't give the following message:
2020-03-18 13:44:17 | INFO | * * * * *
2020-03-18 13:44:17 | INFO | * Purged Everything!
Any advice for things to check or try would be greatly appreciated. I can't tell you how much I appreciate the help.
Just for the record and in order to clarify:
Definately, Webinoly has really softened learning curve with me being new to NGINX and Linux Servers. Thank you so much for that.
I guess I was confused on how to properly request the ssl for my weird/unconventional multisite configuration (that I needed to migrate over). My multisite was aaa.example.org so when I tried to use the Webinoly commands it retrieved the wildcard for *.aaa.example.org instead of *.example.org. How might you have approached that instead by using a Webinoly command?
Purge Cache Issues:
Hey so I think I have new information on my fast-cgi issue.
In the logs when I update the site it shows:
Purging homepage http://aaa.example.org/
... | INFO | - Purging URL | http://aaa.example.org/
... | INFO | - - http://aaa.example.org/ is currently not cached ( checked for file: /var/run/nginx-cache/7/49/be1c5c20d66bca37388e22bd857e8497 )
When I manually purge the current page from the admin bar:
... | INFO | - Purging URL | https://aaa.example.org/
... | INFO | - - https://aaa.example.org/ *** PURGED ***
It seems like the plugin can find the cached files with the admin bar purge command but cannot through the automatic process. Any things you would check in this situation?
Your regular donations is what keep this project moving forward. If you like Webinoly, buy me a coffee or a beer to show support.