autotutorial

NET::ERR_CERT_COMMON_NAME_INVALID this error indicates that you have wrong the name for the certificate domain, it had to be without initial www or If you add www to the url of your site, the certificate is valid, so it is very likely he was wrong for configuration on nginx https://letsencrypt.org/docs/faq/
https://certbot.eff.org/glossary#wildcard-certificate wildcard for all subdomain but not for domain.td

If you add www to the url of your site, the certificate is valid, so it is very likely that you are mistaken for configuration on ngix

it depends on the owner of folders and files, via ftp or with my code it shows you the numbers that indicate the owner … The second method can be uncertain.
Then check from the root until you get wp-content if the owner number is the same.
syntax of the POSIX system UGO.
U for owner (user)
G for group (group user)
O for other (other user)
If it works, leave it like this .. so you have also changed good owner.
https://en.wikipedia.org/wiki/Chmod#Special_modes

sorry we are creating confusion.
If you don’t have phpmyadmin installed please install it.
This is an exhaustive guide to creating the database and the user with the privileges suitable for wordpress. In the field host: create the user with local and not ANY HOST. https://wordpress.org/support/article/creating-database-for-wordpress/#using-phpmyadmin

Now after selecting a user other than root and clicking your database WordPress, repeat the two sql instructions and report the result without a password example

Grants for root@localhost
GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY PASSWORD '*######' WITH GRANT OPTION
GRANT PROXY ON "@" TO 'root'@'localhost' WITH GRANT OPTION'

😉 … even the port.

did you create your user (for external wordpress) without any host? (so only the local user).
What user permissions do you have for that database?
You can use WordPress debug mode if it works ini_set on your server.
Add this before require_once on wp-config.php

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'WP_DEBUG_LOG', true );

default file log is /wp-content/debug.log
also if you don’t work with the object $wpdp which shows the error info only when WP_DEBUG is enabled and the latter works only if you can use ini_set or with external connections to the WordPress $wpdb object if you anticipate errors from your php code (as in this case).
you can check the user who successfully logs in even in sql.
SHOW GRANTS CURRENT_USER;

if the user is with the right permissions and is authorized to access the database externally I would activate the debug only after creating the page before clicking edit and then click on edit and I immediately go to check the debug log .. customize the error from your script so as not to create ambiguity between the user $wpdb object wordpress and the external user database. 😉
https://www.php.net/manual/en/mysqli.connect-error.php

Jolly https://letsencrypt.org/docs/faq/

sorry, I thought you knew the programming, my mistake, forgive me.

I’ll give you an example, I install wordpress in a subdirectory named wp.
my absolute local path is
/home/username/www/wp/
then the ABSPATH constant was created to avoid ambiguously in the path of where wordpress resides.
define('ABSPATH',dirname(__FILE__).'/');
This is the same as the first path I wrote if wp-config.php or wp-settings.php is located in the wp directory.

the correct code for the temp directory inside wp-content is
define('WP_TEMP_DIR',dirname(__FILE__).'/wp-content/temp');
try setting the right permissions:

Read 4 – Allowed to read files
Write 2 – Allowed to write/modify files
eXecute1 – Read/write/delete/modify/directory

Changing File Permissions

Then try setting the wp-content folder and the temporary folder to 777.
If it works for you we have to do other tests to understand how to limit the permissions 🙂

you must also verify the owner file WordPress (wp-settings.php, /wp-content/ etc..) and therefore request support for your hosting for this.
Create test.php into folder WordPress

<?php
$a[] = fileowner(dirname(__FILE__).'/');
clearstatcache();
$a[] = fileowner(dirname(__FILE__).'/wp-settings.php');
clearstatcache();
$a[] = fileowner(dirname(__FILE__).'/wp-content/');
clearstatcache();
print_r($a);

This number is equal?

What permissions do you have in the wp-content folder?

Hi, the error comes from a plugin.
write in the plugin support area. https://wordpress.org/support/plugin/custom-sidebars