Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL_ERROR_INTERNAL_ERROR_ALERT #231

Open
com2 opened this issue Oct 19, 2023 · 1 comment
Open

SSL_ERROR_INTERNAL_ERROR_ALERT #231

com2 opened this issue Oct 19, 2023 · 1 comment

Comments

@com2
Copy link

com2 commented Oct 19, 2023

Describe the bug
entrypoint.sh errors when starting the image:
Line unrecognized: `PrivateKey='
Configuration parsing error

To Reproduce
Steps to reproduce the behavior:

  1. $ docker create
    --name subspace
    --restart always
    --network host
    --cap-add NET_ADMIN
    --volume /usr/bin/wg:/usr/bin/wg
    --volume /data/subspace:/data
    --volume /lib/aarch64-linux-gnu/libc.so.6:/lib/aarch64-linux-gnu/libc.so.6:ro
    --volume /lib/ld-linux-aarch64.so.1:/lib/ld-linux-aarch64.so.1:ro
    --env SUBSPACE_HTTP_HOST="sub.domain.net"
    --env SUBSPACE_NAMESERVER="1.1.1.1"
    subspacecommunity/subspace:arm64v8-v1.5.0
  2. $ docker start subspace; docker logs subspace >& subspace.log ; tail subspace.log
  • export 'SUBSPACE_IPV4_CIDR=24'
  • ip addr add 10.99.97.1/24 dev wg0
  • '[[' 1 -ne 0 ]]
  • echo fd00::10:97:0/112
  • cut -d / -f2
  • export 'SUBSPACE_IPV6_CIDR=112'
  • ip addr add fd00::10:97:1/112 dev wg0
  • wg setconf wg0 /data/wireguard/server.conf
    Line unrecognized: `PrivateKey='
    Configuration parsing error

Expected behavior
Start without error and working web access.

Docker host server :

  • OS: Debian arm64
  • Version 12
  • Docker version 24.0.6, build ed223bc
@com2 com2 changed the title What are the correct arm64 --volume parameters? Line unrecognized: `PrivateKey=' Configuration parsing error Oct 23, 2023
@com2
Copy link
Author

com2 commented Oct 23, 2023

When looked in /data/subspace/wireguard/ both server.private and server.public are empty (zero length), but the files and the wireguard folder exist. So it turns out that something was written in previous attempts. I stop de image, delete the wireguard folder and start it again. Ports 80 and 443 are open now, the web service seems to be running, but now something might have gone wrong with Let's Encrypt and the browser tells me:

Secure Connection Failed

An error occurred during a connection to zibaliqpos.serverclone.net. Peer reports it experienced an internal error.

Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

A link to Mozilla support lists the possible reasons.

@com2 com2 changed the title Line unrecognized: `PrivateKey=' Configuration parsing error SSL_ERROR_INTERNAL_ERROR_ALERT Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant