SSL_ERROR_INTERNAL_ERROR_ALERT without clue

ℹ️ Support
,
1

Hello everybody,

I’m in trouble running AIO for the first time without reverse proxy. I came across the whole Github process without trouble, then started my AIO instance and tried to connect to my fresh Nextcloud. Suprisingly, I got this Error : SSL_ERROR_INTERNAL_ERROR_ALERT ( No error code on the browser)

After checking some topics (on this forum, on Github and on other platform), I didn’t found any case where my error is described.

In fact, I didn’t get any error in my logs :

Apache logs (sudo docker logs nextcloud-aio-apache):

logs_apache
logs_apache1552×137 9.93 KB

Mastercontainer logs :

logs master_container
logs master_container1213×130 8.92 KB

That’s why now, I’m asking you whether you have any idea to fix this.

Nextcloud version (eg, 20.0.5): Same version than the latest AIO
Operating system and version : Debian Bullseye 11
Apache or nginx version (eg, Apache 2.4.25): Same version than the latest AIO
Port are 443 is open and accessible.

Thank you in advance :smiley:

2

Hi, see What can I do when Nextcloud is not reachable via my domain or if I get `SSL_ERROR_INTERNAL_ERROR_ALERT` or `ERR_SSL_PROTOCOL_ERROR` when opening my Nextcloud domain? · nextcloud/all-in-one · Discussion #2105 · GitHub

1 Like
3

Re ! Thank you for the interesting reply :smiley:

After investigation, I think I got the real problem :

My domain is actually a sub-domain of noip (platform for free ip).
It looks like this : mydomain.hopto.org

So Nextcloud can not validate the certificate on my domain and give me an error.

It exist at least two solution :

A) I configure Apache to create a nextcloud.mydomain.hopto.org sub-domain and point it to my IP address. It requires precise configuration and I need to search about it on the web.

B) I get a “true” domain name and re-install AIO / point Nextcloud on this new domain

What do you think about the problem and the solution ? Do you have any advice ?

4

Can you post the output of sudo docker logs nextcloud-aio-apache here?

5

I didn’t try to fix anything for the moment, here are the logs :

user@machine:~$ **sudo docker logs nextcloud-aio-apache** [Tue Dec 26 09:11:37.531615 2023] [mpm_event:notice] [pid 48:tid 139814917450568] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations [Tue Dec 26 09:11:37.531678 2023] [core:notice] [pid 48:tid 139814917450568] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' {"level":"info","ts":1703581897.534068,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""} {"level":"info","ts":1703581897.5374346,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."} {"level":"info","ts":1703605086.1589277,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""} [Tue Dec 26 15:38:06.164674 2023] [mpm_event:notice] [pid 45:tid 140077388122952] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations [Tue Dec 26 15:38:06.164737 2023] [core:notice] [pid 45:tid 140077388122952] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' {"level":"info","ts":1703605086.1686587,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."} {"level":"info","ts":1703671446.6877553,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""} [Wed Dec 27 10:04:06.695199 2023] [mpm_event:notice] [pid 46:tid 140489499241288] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations [Wed Dec 27 10:04:06.695230 2023] [core:notice] [pid 46:tid 140489499241288] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' {"level":"info","ts":1703671446.697814,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."} {"level":"info","ts":1703746989.65225,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""} [Thu Dec 28 07:03:09.659752 2023] [mpm_event:notice] [pid 47:tid 140213411302216] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations [Thu Dec 28 07:03:09.660075 2023] [core:notice] [pid 47:tid 140213411302216] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' {"level":"info","ts":1703746989.6620142,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."} {"level":"info","ts":1703759223.1548953,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""} [Thu Dec 28 10:27:03.163591 2023] [mpm_event:notice] [pid 47:tid 139984613116744] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations [Thu Dec 28 10:27:03.163631 2023] [core:notice] [pid 47:tid 139984613116744] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND' {"level":"info","ts":1703759223.1650987,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}

6

There are no further logs?

7

Nop, there are no further log using this command. Here are the log of the master container if that can help. Everything seems okay, that’s why I don’t understand the SSL Error.

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: https://your-domain-that-points-to-this-server.tld:8443 {"level":"info","ts":1703746972.2000978,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""} [Thu Dec 28 07:02:52.339821 2023] [mpm_event:notice] [pid 128:tid 139776256662344] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations [Thu Dec 28 07:02:52.339850 2023] [core:notice] [pid 128:tid 139776256662344] AH00094: Command line: 'httpd -D FOREGROUND' [28-Dec-2023 07:02:52] NOTICE: fpm is running, pid 133 [28-Dec-2023 07:02:52] NOTICE: ready to handle connections Initial startup of Nextcloud All-in-One complete! You should be able to open the Nextcloud AIO Interface now on port 8080 of this server! E.g. https://internal.ip.of.this.server:8080
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: https://your-domain-that-points-to-this-server.tld:8443 {"level":"info","ts":1703759204.152652,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""} [Thu Dec 28 10:26:44.263473 2023] [mpm_event:notice] [pid 124:tid 140108680612680] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations [Thu Dec 28 10:26:44.263507 2023] [core:notice] [pid 124:tid 140108680612680] AH00094: Command line: 'httpd -D FOREGROUND' [28-Dec-2023 10:26:44] NOTICE: fpm is running, pid 130 [28-Dec-2023 10:26:44] NOTICE: ready to handle connections

8

Hm, can you try to open your domain from outside your network, e.g. from mobile via LTE?

9

Thank you :smiley:
It works with my mobile on LTE network !

So I can do a network sharing with my laptop to access to my Nextcloud.

Nevertheless, do you have any advices to acces through my local network (Wifi or Ehernet) . That woud be cool to access directly without switching network each time.

10

See https://github.com/nextcloud/all-in-one#how-can-i-access-nextcloud-locally

11

Thank you for your support and for the advices, I will work on it :+1: