Issue is upstream
https://github.com/acmesh-official/acme.sh/issues/1914
https://github.com/acmesh-official/acme.sh/issues/1743
https://github.com/acmesh-official/acme.sh/issues/1914
it seems to be fixed in the development branch,
but the fix is not yet in the main release
fixes:
Run development release
```
acmesh --upgrade -b dev
```
Add Config path after in activateSSL-<Domain>.sh
Before:
```
if [ $domainwww = 1 ]; then
/opt/acmesh/acme.sh --config-home '/etc/acmesh/data' --issue --"$webserv" --ocsp --keylength 'ec-384' -d "$domain" -d "www.$domain"
certsatus=$?
elif [ $domainwww = 0 ]; then
/opt/acmesh/acme.sh --config-home '/etc/acmesh/data' --issue --"$webserv" --ocsp --keylength 'ec-384' -d "$domain"
certsatus=$?
fi
```
After:
```
if [ $domainwww = 1 ]; then
/opt/acmesh/acme.sh --config-home '/etc/acmesh/data' --issue --"$webserv" "/etc/nginx/sites-enabled/$sitename" --ocsp --keylength 'ec-384' -d "$domain" -d "www.$domain"
certsatus=$?
elif [ $domainwww = 0 ]; then
/opt/acmesh/acme.sh --config-home '/etc/acmesh/data' --issue --"$webserv" "/etc/nginx/sites-enabled/$sitename" --ocsp --keylength 'ec-384' -d "$domain"
certsatus=$?
fi
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue is upstream
https://github.com/acmesh-official/acme.sh/issues/1914
https://github.com/acmesh-official/acme.sh/issues/1743
https://github.com/acmesh-official/acme.sh/issues/1914
it seems to be fixed in the development branch,
but the fix is not yet in the main release
fixes:
Run development release
Add Config path after in activateSSL-.sh
Before:
After:
Fixed in upstream Main/
Masterbranch