Scripted installation of Nextcloud 28 in iocage jail 2018-03-23

[danb35]

Not quite sure what the problem is

This sounds suspiciously like the directory being used for files has Windows permissions, which will break things. Can you check that?

(Oops, as I see from reading the thread, you've already found that to be the case). I should probably add that to the README (and update the script to check for it, if I can figure out how).

 

[Kuro Houou]

Ok new question, is there an easy way to change the user that nextcloud runs as? Right now looks like its using the www user, which makes uploading photos from the app impossible as my photos folder is again a Windows permissioned folder and in Freenas, the www user is purely a unix user account.. so I can't assign it as a user in Windows security permissions... I have another user from my old nextcloud instance I could use... www-data.. anyway I can make nextcloud run as that? Or is there a better way to do this.. I figure 90% of the people here probably have a windows permissioned folder that they want nextcloud to access and be able to write to?

 

[Kuro Houou]

Is there anyway we could specify during install if we want to use Windows based permissions instead, or install onto a Windows based dataset?

And thanks danb35 and apollo. I was using a central apps folder for my jails.. but apparently because it was in a folder that was the windows permission type, that's what caused the issues with the script.. so now I have another dataset/folder for nextcloud that is unix permissioned. Thats when the install script installed ok..

This sounds suspiciously like the directory being used for files has Windows permissions, which will break things. Can you check that?

(Oops, as I see from reading the thread, you've already found that to be the case). I should probably add that to the README (and update the script to check for it, if I can figure out how).

 

[Kuro Houou]

Think I found the work around.. I just did a chown www:wheel on my folder I want Nextcloud to have write access too.. not sure if thats the best option but I think thats the only way you can write to other mounted folders to the jail.

 

[plisken]

Can this script be used to upgrade from 16.05 to 17 and keep the "files" data folder intact and show up in NC-17?

 

[Apollo]

Can this script be used to upgrade from 16.05 to 17 and keep the "files" data folder intact and show up in NC-17?

If you have 16.05 installed already, then you could update directly from within Nextcloud web. You have to make sure your packages are up to date and you meet NC17 requirements.

 

[plisken]

So I updated the packages with “pkg update && pkg upgrade” stoped and restarted the jail, logged into the web Ui but still no option to update to 17. If I were to create a new Nextcloud jail and use the existing “files” folder in the script setup will the files show up in Nextcloud 17 or Will is files be over written during the installation?

 

[danb35]

pkg update && pkg upgrade

Don't do this; pkg isn't apt. A simple pkg upgrade will do.

As to the upgrade, no, a new installation mapped to an existing files/ path will not show all the existing files, as they're stored in the database. I'd investigate why Nextcloud isn't offering the upgrade--are you logged in as admin? If so, I'd expect it should show it. You could always do the upgrade manually through the shell, but that's far from ideal.

 

[Apollo]

Don't do this; pkg isn't apt. A simple pkg upgrade will do.

As to the upgrade, no, a new installation mapped to an existing files/ path will not show all the existing files, as they're stored in the database. I'd investigate why Nextcloud isn't offering the upgrade--are you logged in as admin? If so, I'd expect it should show it. You could always do the upgrade manually through the shell, but that's far from ideal.

I think the only way to upgrade is to enable Beta in Nextcloud as the release is not yet official I believe.

 

[danb35]

the release is not yet official I believe.

No, NC17 was released on 26 Sep, so it's definitely "official." However, it's true that there's often a delay in pushing updates out, and that could account for it not being there yet. If that's the case, then yes, switching to the Beta channel may work, or it might be better to just wait for 17 to show up in the updater.

Edit: I can confirm that if you switch to the Beta channel, 17.0 appears as an update option. It isn't beta--it's a full release (as of a month ago)--but apparently it hasn't been pushed out to the stable update channel yet. But it upgrades just fine for me, and that's after loading about 15 GB of test data into the instance.

 

[capio]

Hello, when i try to connect it says ERR_CONNECTION_REFUSED. Dont know why. Any suggestions?

 

[capio]

EDIT: i tried in LAN. 192.168.178.80 in google chrome

 

[danb35]

You shouldn't expect to be able to connect to your Nextcloud installation using the IP address of the jail--you need to use the name instead. But even then, that wouldn't get you a "connection refused" error--that suggests instead that Caddy isn't running at all. What does your nextcloud-config file look like? Is there anything noteworthy in /var/log/caddy.log in the jail?

 

[Thomas_VDB]

Hi,
Been using scripted nextcloud on my freenas hapilly for a few months now. Mostly via web-interface to see/download files.
Now I have installed the nextcloud client for windows on my laptop, and everything is syncing ok. However I am not allowed to edit/upload files. No permissions error in nextcloud client. Been googling but as I am no freebsd nor Linux expert, it's difficult to debug this problem. Can someone please advise? Thx!

 

[Charlie86]

Hi,

Sorry for noob question.

I am trying to install nextcloud via script but having issues with version of Freenas.

I am running FreeNAS-11.1-U7

When I try tu run script I get error:

11.1-RELEASE was not found!

What am I doing wrong?

 

[danb35]

11.1-RELEASE was not found!

Is that the only thing it says, or is there more to the output? As a first guess, I'd say that 11.1 is old enough that it isn't available any more as a release for a jail, but there should be more context that would clarify things.

 

[Charlie86]

Hi,

down is more detailed view of my problem.



charlie@freenas:~ % cd freenas-iocage-nextcloud/ charlie@freenas:~/freenas-iocage-nextcloud % sudo ./nextcloud-jail.sh ls: /mnt/aja/db: No such file or directory 11.1-RELEASE was not found! Failed to create jail

 

[capio]

You shouldn't expect to be able to connect to your Nextcloud installation using the IP address of the jail--you need to use the name instead. But even then, that wouldn't get you a "connection refused" error--that suggests instead that Caddy isn't running at all. What does your nextcloud-config file look like? Is there anything noteworthy in /var/log/caddy.log in the jail?

hey, thanks for your answer. i havent found the config. can you tell me where to find it? i used "find" but didnt work.

heres my caddy.log. do you know how to fix this issue?
best regards


root@nextcloud:/ # cat /var/log/caddy.log
Activating privacy features... 2019/10/21 22:37:40 [INFO][cache:0xc0000c0820] Started certificate maintenance routine
2019/10/21 22:37:46 [INFO] acme: Registering account for *****@gmail.com
2019/10/21 22:37:47 [INFO][nextcloudden] Obtain certificate
2019/10/21 22:37:47 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:47 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=http-01)
2019/10/21 22:37:48 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:48 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=http-01)
2019/10/21 22:37:49 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:49 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=http-01)
2019/10/21 22:37:50 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:50 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=tls-alpn-01)
2019/10/21 22:37:51 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:51 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=tls-alpn-01)
2019/10/21 22:37:53 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 22:37:53 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=tls-alpn-01)
2019/10/21 22:37:54 failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url:
Activating privacy features... 2019/10/21 23:54:56 [INFO][cache:0xc0001c2320] Started certificate maintenance routine
2019/10/21 23:55:02 [INFO][nextcloudden] Obtain certificate
2019/10/21 23:55:02 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:02 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=http-01)
2019/10/21 23:55:03 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:03 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=http-01)
2019/10/21 23:55:04 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:05 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=http-01)
2019/10/21 23:55:06 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:06 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=tls-alpn-01)
2019/10/21 23:55:07 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:07 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=tls-alpn-01)
2019/10/21 23:55:08 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/21 23:55:08 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=tls-alpn-01)
2019/10/21 23:55:09 failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url:
Activating privacy features... 2019/10/24 21:19:51 [INFO][cache:0xc0001e4320] Started certificate maintenance routine
2019/10/24 21:19:52 [INFO][nextcloudden] Obtain certificate
2019/10/24 21:19:52 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:53 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=http-01)
2019/10/24 21:19:54 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:54 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=http-01)
2019/10/24 21:19:55 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:55 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=http-01)
2019/10/24 21:19:56 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:56 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=tls-alpn-01)
2019/10/24 21:19:57 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:58 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=tls-alpn-01)
2019/10/24 21:19:59 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:19:59 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=tls-alpn-01)
2019/10/24 21:20:00 failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url:
login class 'daemon' non-existent, using default
Activating privacy features... 2019/10/24 21:20:41 [INFO][cache:0xc0001ae320] Started certificate maintenance routine
2019/10/24 21:20:42 [INFO][nextcloudden] Obtain certificate
2019/10/24 21:20:42 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:42 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=http-01)
2019/10/24 21:20:43 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:44 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=http-01)
2019/10/24 21:20:45 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:45 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=http-01)
2019/10/24 21:20:46 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:46 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 1/3; challenge=tls-alpn-01)
2019/10/24 21:20:47 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:47 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 2/3; challenge=tls-alpn-01)
2019/10/24 21:20:48 [INFO] [nextcloudden] acme: Obtaining bundled SAN certificate
2019/10/24 21:20:48 [ERROR][nextcloudden] failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url: (attempt 3/3; challenge=tls-alpn-01)
2019/10/24 21:20:49 failed to obtain certificate: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "nextcloudden": DNS name does not have enough labels, url:

 

[capio]

Hello, i reinstalled. this is my new log:


root@nextcloud:/ # cat /var/log/caddy.log
Activating privacy features... 2019/10/27 00:13:48 [INFO][cache:0xc0001d6320] Started certificate maintenance routine
2019/10/27 00:13:49 [INFO] acme: Registering account for ****@gmail.com
2019/10/27 00:13:49 [INFO][dennis.hopto.org] Obtain certificate
2019/10/27 00:13:49 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:13:50 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004442
2019/10/27 00:13:50 [INFO] [dennis.hopto.org] acme: use tls-alpn-01 solver
2019/10/27 00:13:50 [INFO] [dennis.hopto.org] acme: Trying to solve TLS-ALPN-01
2019/10/27 00:14:04 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004442
2019/10/27 00:14:04 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Timeout during connect (likely firewall problem), url:
(attempt 1/3; challenge=tls-alpn-01)
2019/10/27 00:14:05 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:14:05 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004480
2019/10/27 00:14:05 [INFO] [dennis.hopto.org] acme: use tls-alpn-01 solver
2019/10/27 00:14:05 [INFO] [dennis.hopto.org] acme: Trying to solve TLS-ALPN-01
2019/10/27 00:14:18 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004480
2019/10/27 00:14:18 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Timeout during connect (likely firewall problem), url:
(attempt 2/3; challenge=tls-alpn-01)
2019/10/27 00:14:19 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:14:19 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004512
2019/10/27 00:14:19 [INFO] [dennis.hopto.org] acme: use tls-alpn-01 solver
2019/10/27 00:14:19 [INFO] [dennis.hopto.org] acme: Trying to solve TLS-ALPN-01
2019/10/27 00:14:37 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004512
2019/10/27 00:14:37 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Timeout during connect (likely firewall problem), url:
(attempt 3/3; challenge=tls-alpn-01)
2019/10/27 00:14:38 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:14:38 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004553
2019/10/27 00:14:38 [INFO] [dennis.hopto.org] acme: Could not find solver for: tls-alpn-01
2019/10/27 00:14:38 [INFO] [dennis.hopto.org] acme: use http-01 solver
2019/10/27 00:14:38 [INFO] [dennis.hopto.org] acme: Trying to solve HTTP-01
2019/10/27 00:15:02 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004553
2019/10/27 00:15:02 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Fetching http://dennis.hopto.org/.well-known/acme-challenge/I5neG0HkMVsVjjAL0id6sQwdjvXZ8By3pMiJwE_2RhI: Timeout during connect (likely firewall problem), url:
(attempt 1/3; challenge=http-01)
2019/10/27 00:15:03 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:15:03 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004593
2019/10/27 00:15:03 [INFO] [dennis.hopto.org] acme: Could not find solver for: tls-alpn-01
2019/10/27 00:15:03 [INFO] [dennis.hopto.org] acme: use http-01 solver
2019/10/27 00:15:03 [INFO] [dennis.hopto.org] acme: Trying to solve HTTP-01
2019/10/27 00:15:35 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004593
2019/10/27 00:15:35 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Fetching http://dennis.hopto.org/.well-known/acme-challenge/OdqwWaOqIbQkqlhxmJrYGkUsY-xmmleNPjBk25QDp8s: Timeout during connect (likely firewall problem), url:
(attempt 2/3; challenge=http-01)
2019/10/27 00:15:36 [INFO] [dennis.hopto.org] acme: Obtaining bundled SAN certificate
2019/10/27 00:15:36 [INFO] [dennis.hopto.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004666
2019/10/27 00:15:36 [INFO] [dennis.hopto.org] acme: Could not find solver for: tls-alpn-01
2019/10/27 00:15:36 [INFO] [dennis.hopto.org] acme: use http-01 solver
2019/10/27 00:15:36 [INFO] [dennis.hopto.org] acme: Trying to solve HTTP-01
2019/10/27 00:16:06 [INFO] Unable to deactivated authorizations: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/17004666
2019/10/27 00:16:06 [ERROR][dennis.hopto.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Fetching http://dennis.hopto.org/.well-known/acme-challenge/aDE7mLyFZ9R03GZw3aCBAL02CmjNsQUVTOPRgGBFHNM: Timeout during connect (likely firewall problem), url:
(attempt 3/3; challenge=http-01)
2019/10/27 00:16:07 failed to obtain certificate: acme: Error -> One or more domains had a problem:
[dennis.hopto.org] acme: error: 400 :: urn:ietf:params:acme:error:connection :: Fetching http://dennis.hopto.org/.well-known/acme-challenge/aDE7mLyFZ9R03GZw3aCBAL02CmjNsQUVTOPRgGBFHNM: Timeout during connect (likely firewall problem), url:

 

[danb35]

i havent found the config. can you tell me where to find it?

You would have created it, in the directory where you placed the script.

Timeout during connect (likely firewall problem),

Here's your error, and the likely cause. You need to have port 443 on your jail open to the Internet.