Webinoly is just the perfect tool for NGINX experts. Give it a try!
0 votes
by Rookie


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.

  1. Is webinoly capable of automatically getting a wildcard cert correctly for my configuration? 
  2. What is the current state/what are my options to setup fastcgi cache? I can't tell from this forum and the documentation if there is any way of configuring it. Through my research it looks like I would need the purge module, but that isn't recommended from Webinoly. Any reccomendations?

1 Answer

0 votes
by Expert

Yes, Webinoly have SSL wildcard support.

And yes, Webinoly have FastCGI Cache support and you don't need the purge module, this module is only needed for shared hosting environments.

Please, read the documentation.
by Rookie

Hey Cristhian,

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?

by Expert
In the "site" command documentation, please read about the "-cache" and "-add-to-wildcard" options.
by Rookie

(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 email@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!

2020-03-18 13:44:17  | INFO | * * * * *

Any advice for things to check or try would be greatly appreciated. I can't tell you how much I appreciate the help.

by Expert

Just for the record and in order to clarify:

  • You can request a wildcard cert directly from Webinoly.
  • With Webinoly you don't need to touch any lines of code or configuration, even if you have your own cert, Webinoly has an option to add it to your site and server automatically.
That's exactly why Webinoly exists, to avoid and skip all of these complicated and manual steps.
About the purge-cache issues:
  • Check the Nginx-Helper settings about conditional purging.
  • Use the Nginx-Helper timestamp feature.
  • Remember that signed-in users always see fresh and uncached versions.
by Rookie

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:

  • I've tried disabling the conditional settings and enabling them. According to the nginx helper logs it looks like it's working but not quite finishing the purging (as seen in previous comment). Anything else you would try?
  • I did turn on the timestamp feature and will try to use that to help troubleshoot.
  • Right, I've been opening up new a new incognito page to test the caching. Caching has been working great after manually purging the page from the admin panel at the top of the page.
Again I appreciate your patience and help!
by Expert
You can do a SSL (wildcard) cert request for whatever domain you want (example.org) and then you can add (-add-to-wildcard) any subdomain (aaa.example.org and bbb.example.org) to this cert. It's that simple!
by Rookie
edited by

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?

by Rookie
My issue ended up being that in my wordpress site url in the wordpress settings was set to http instead of https. As you can see in the above log, I think Nginx Helper saw the page get updated but looked for the http version instead of the https version. I made this change and reloaded nginx and it looks like it's working correctly.
by Expert
Glad you solved your issue!

Now that you mention it, Webinoly automatically updates this value in WP database when SSL is created, but now I'm thinking that it won't work with the "-add-to-wildcard" option. I'm gonna fix it in the next release (v.1.11.0).

by Expert
This issue has been fixed in v1.11.0, released today.
Welcome to the Community site for Webinoly.

Our Optimized LEMP Web Server is a powerful set of commands for doing just about anything you could wish.

With Webinoly you can set up your NGINX web server in just one step.

* * * * * * *

To report a bug, please create a new issue on GitHub or ask a question here with the bug tag.
Webinoly Support Paypal Donations

PayPal · GitHub Sponsors · Bitcoin

It is very important that any visitor to the site read the disclaimer, terms of use and privacy and legal statement before start browsing.