Root@pc:~/ ./ --issue -d -> connection refused

My domain is:

I ran these commands:

marco@pc: su -

root@pc:~# git clone
Cloning into ''...
remote: Enumerating objects: 9055, done.
remote: Total 9055 (delta 0), reused 0 (delta 0), pack-reused 9055
Receiving objects: 100% (9055/9055), 3.52 MiB | 5.25 MiB/s, done.
Resolving deltas: 100% (5275/5275), done.

root@pc:~/ apt-get install socat
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed
0 to upgrade, 1 to newly install, 0 to remove and 7 not to upgrade.
Need to get 342 kB of archives.
After this operation, 1,034 kB of additional disk space will be used.
Get:1 bionic/main amd64 socat amd64 [342 kB]
Fetched 342 kB in 10s (33.5 kB/s)
Selecting previously unselected package socat.
(Reading database ... 116435 files and directories currently installed.)
Preparing to unpack .../socat_1.7.3.2-2ubuntu2_amd64.deb ...
Unpacking socat ( ...
Setting up socat ( ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...

root@pc:~/ ./ --install
[Sat 10 Aug 13:18:50 CEST 2019] Installing to /root/
[Sat 10 Aug 13:18:50 CEST 2019] Installed to /root/
[Sat 10 Aug 13:18:50 CEST 2019] Installing alias to '/root/.bashrc'
[Sat 10 Aug 13:18:50 CEST 2019] OK, Close and reopen your terminal to start using
[Sat 10 Aug 13:18:50 CEST 2019] Installing cron job
23 0 * * * "/root/"/ --cron --home "/root/" > /dev/null
[Sat 10 Aug 13:18:50 CEST 2019] Good, bash is found, so change the shebang to use bash as 
[Sat 10 Aug 13:18:50 CEST 2019] OK

root@pc:~/ ./ --issue -d -w /home/wwwroot/ -d 
--force --debug

It produced this output: error:Fetching  
/4UdH8TuPksZloqCWHNbhjy4C9L5Iw8V0JguBvNFKvGA: Connection refused

This is the complete debug file: (16.9 KB)

My web server is (include version): nginx version: nginx/1.14.0 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 18.04.02 Server Edition

I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

Looking forward to your kind help.

Resolved. Now the only question left is: how to automatically renew the certificates with

by default creates a cron job to do that:

[Sat 10 Aug 13:18:50 CEST 2019] Installing cron job
23 0 * * * “/root/”/ --cron --home “/root/” > /dev/null

Thank you. I modified the crontab as follows:

0 */12 * * * “/root/”/ --cron --home “/root/” > /dev/null

it not recommended to run that crontab at xx:00, as this could result in high serverload, if many users do so. That why the first number is typically a random one.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.