Are we sure CertSage is the best client for this?
2 Likes
Not necessarily. Given the age of the OS and the situation, I figured it called for a simple solution with few dependencies.
1 Like
I can't understand what the problem is, there are rights to the folder and the file, the path is registered in the config, I don't know what else can be done, tomorrow is the last day and the mail certificate will end (((
1 Like
You might want to try one of the Bash ACME client such as getssl (it has pretty good documentation, such as an extensive howto) or acme.sh as stated earlier.
2 Likes
maybe you will send another client and instructions as you wrote earlier, I'll try to deliver, suddenly it will work out
1 Like
Honestly, given the problems you've encountered with trying to get your Apache webserver to serve files, you would probably be better off trying to use dns-01 authentication (manual) instead of http-01 authentication (webroot). The clients that @Osiris recommended should work for dns-01.
1 Like
Good afternoon, I decided to try through another browser to go on the link, it went, after entered the data and pressed the button gets out 500 errors, what could it mean?
1 Like
The 500 errors are usually the result of the PHP version being too old. When I try to access http://mail.ivanovoobl.ru/certsage.php, I still get 403 Forbidden. Is there an error log file in the directory with certsage.php?
1 Like
tell me how the log file should be called?
1 Like
Depends on your PHP. Usually something like error_log.txt or errorlog.txt.
1 Like
I looked at the root where certsage.php and there are no similar files anywhere in the folders nearby
1 Like
Download this file:
phpinfo.txt (19 Bytes)
Put it in the same folder as certsage.php then change its file extension from txt to php.
Visit http://mail.ivanovoobl.ru/phpinfo.php then take a screenshot. Be sure the screenshot includes the PHP version. You might need several screenshots to capture everything.
1 Like
I am trying to update PHP, gives an error of repositories
sudo apt-get update
sudo apt-get install apt-transport-https lsb-release ca-certificates
sudo wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg
sudo sh -c 'echo "deb Index of /php/ $(lsb_release -sc) main" > /etc/apt/sources.list.d/php.list'
sudo apt-get update
sudo apt-get install php8.0
In the end he writes, I tried version from 7 to 8
W: Недоступен открытый ключ для следующих ID ключей:
AA8E81B4331F7F50
W: Не удалось получить http://mirror.yandex.ru/debian/dists/jessie-backports/main/source/Sources 404 Not Found [IP: 213.180.204.183 80]
W: Не удалось получить http://mirror.yandex.ru/debian/dists/jessie-backports/main/binary-amd64/Packages 404 Not Found [IP: 213.180.204.183 80]
W: Не удалось получить https://packages.sury.org/php/dists/jessie/main/binary-amd64/Packages HttpError404
W: Не удалось получить http://cdn.debian.net/debian/dists/jessie-backports/main/binary-amd64/Packages 404 Not Found [IP: 199.232.150.132 80]
W: Не удалось получить http://cdn.debian.net/debian/dists/jessie-backports/contrib/binary-amd64/Packages 404 Not Found [IP: 199.232.150.132 80]
W: Не удалось получить http://cdn.debian.net/debian/dists/jessie-backports/non-free/binary-amd64/Packages 404 Not Found [IP: 199.232.150.132 80]
E: Некоторые индексные файлы не скачались. Они были проигнорированы или вместо них были использованы старые версии.
1 Like
What version is currently shown when you visit phpinfo.php?
1 Like
the version is the same because it was not possible to update
1 Like
What can you try?
1 Like
Although it has been mentioned (more than once) on this thread, here is an aide for the visually needy:
1 Like
I don't quite understand what to do, this picture shows the dates of support for different versions of debian or something else, if possible, I would like something specific that can be done now, thanks
2 Likes
I would need the error message from a log to know specifically what's happening. I've tried to make CertSage as backward compatible as possible with earlier PHP releases, but yours might be just a bit too far back I'm afraid. Installing certbot on a different system, satisfying a dns-01 challenge, then securely transferring the certificate and private key to your mail system may be the most expedient solution. Even if we were to manage to get CertSage (or any http-01 ACME client) running on your mail server, the restricted nature of accessing your server with HTTP(S) will likely hinder satisfying an http-01 challenge.
1 Like