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

Updated to v1.11

Set up the LetsEncrypt environment...

sudo webinoly -conf-value_debug=true

Cloned a staging site from the production site... 

sudo site dev.domain.tld -clone-from=domain.tld

Activated SSL... 

sudo site dev.domain.tld -ssl=on

Now I get "NET::ERR_CERT_AUTHORITY_INVALID" when I try to access the staging site with either Chrome or Firefox

What am I doing wrong?

Terence.

1 Answer

+1 vote
by Expert

With debug=true you are setting the "staging" Let's Encrypt environment, so you are not getting real certs. This is used to get certs for testing purposes only, I'm sure you got a warning message in Webinoly after you requested that cert.

by Talented
Yes I id but I thought the staging certificates would allow the browser to access the staging site. Apparently they do but I haven't figured out quite how yet.  I just read  at letsencrypt.org "If you wish to modify a test-only client to trust the staging environment for testing purposes you can do so by adding the “Fake LE Root X1” certificate to your testing trust store."  But I haven't figured out yet exactly what that means in this context.
by Expert
Just follow the instructions in your browser. I don't have how to test it right now, but in the error message there's always a link for "advanced" option or something like that, then you are allowed to force the browser to ignore this error.
by Talented
Cool, I'll go look for that.
by Talented

A basic how-to on how to use Webinoly to set up, use and manage a staging site would be helpful (in your copious free time laugh).

by Expert

One minute tutorial:

  • Create a "staging" site, let's say: sudo site dev.example.com -wp (you don't need cache or ssl at this point).
  • Do all the magic you know how to do to deliver the most awesome site to your client.
  • Now you are ready to send it to production: sudo site example.com -clone-from=dev.example.com
  • And finally, you can activate SSL and Cache, and use the -replace-content option if you want to update some content or links.
That's all!
by Talented
The problem is, my friend, you are encumbered by your own knowledge. We're not all developers, so don't understand the whole process anywhere near as well as you, and for me at least, there are great big holes in that explanation.

Immediately I am thinking about, how should my DNS and Webinoly be set up to create this dev. subdomain, and what about the SSL and wildcard certificate installation. From my own experience of trying to use the clone function on a production site, there's a planning stage and correct order of events which your "one-minute tutorial" doesn't touch on.

But yes, for the simple use-case where you simply want to create a site (whether awesome or not) and show/deliver it to your client, as a top-down view, that's fine.

However, that only explains "cloning" in principle; and not the entire process of using a "staging" site on an ongoing basis. I see them as two parts of the same process, but not the same thing.

For example, your explanation doesn't (wasn't intended to) cover the steps needed and processes for maintenance and updates, especially where it relates to a transactional website using WooCommerce, where you have live transactional changes occurring daily, and you might want to make ongoing design or update changes on the "staging" site, and then move them to the "production" site, when they all check out.

In that scenario there's a fair bit more to be done with backups, Webinoly and DNS management, right?

To give something back, if I wrote such a how-to, in the style of your "Webinoly full example and tutorial", and contributed it to the project for use (or not) as you see fit, would you help me where I get stuck?

It would be helpful to me and help put my thoughts in order, plus I am sure I will learn a lot along the way.

Terence.
by Expert
Sometimes seems like people don't understand that this is an Open Source project, this is a project I do in my free-time, this is a lot of job I do just because I like it, this is a hobby and it's not profitable for me, I do it almost for free, except for some donations I receive from time to time from some awesome people.
by Talented
I understand the words you have written but I am not sure what was your intention in writing them?
by Expert
I really appreciate feedback from users, it's a great opportunity to improve.

The Open-Source soul is about community, maintaining a project like this is a lot of job that I'm happy to do, that's why I do it. But asking for things that only implies more job for me is not the best way to help.

Also, although Webinoly can be very useful to learn about servers, very basic topics like DNS management are totally out of the scope of this project.
by Talented

I wasn't asking for anything, I was offering to do something to help...

To give something back, if I wrote such a how-to, in the style of your "Webinoly full example and tutorial", and contributed it to the project for use (or not) as you see fit, would you help me where I get stuck?

So never mind I have plenty to do with my time also.

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.

...