Problem after update from 1.17 to 1.18

[nebulon]

So this seems to happen when the app tries to connect to the OpenID provider. That one is hosted on your dashboard domain (my.domain.com) and the app needs to be able to reach that.
Seems like the routing works but there is some SSL issue.

Can you open a webterminal into the meemo app and check if curl -v https://my.<YOURDOMAIN.COM>/.well-known/openid-configuration works from there?

[girish]

Do you use self-signed certs?

[vojtam]

@nebulon :
root@d66e914e-fd7a-4b20-bf07-622a70a2f2d8:/app/code# curl -v https://my.vojtam.net/.well-known/openid-configuration

• Trying 87.236.195.190:443...
• Connected to my.vojtam.net (87.236.195.190) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• CAfile: /etc/ssl/certs/ca-certificates.crt
• CApath: /etc/ssl/certs
• TLSv1.0 (OUT), TLS header, Certificate Status (22):
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• (5454) (IN), , Unknown (72):
• error:0A00010B:SSL routines::wrong version number
• Closing connection 0
  curl: (35) error:0A00010B:SSL routines::wrong version number

[vojtam]

@girish: I use Let's Encrypt cert - default generated from Cloudron

[girish]

I think this is an issue with minBoxVersion not set properly @nebulon .

@vojtam which version of Cloudron are you on? You need to be on 7.5 atleast. Looks like you are in a old version of Cloudron.

[vojtam]

@girish: I have Cloudron v7.6.0 installed 19.10.2023

[girish]

@vojtam One more test. Does that curl command work on the host? If not, I would try to debug why curl -v https://my.vojtam.net/ does not work. Do you have a proxy in the front or some other special setup?

edit: are you hosting at home by any chance? If so, does your router support hairpin routing? How do you access your Cloudron from inside the network?

[vojtam]

@girish from cloudron server is command "curl -v https://my.vojtam.net/ " success .
The server is in the data center and cloudron server is a virtual...
Ports 80 and 443 are forward to cloudron server.

[vojtam]

When i use Meemo 1.17 everything it worked fine... except public notes (but this bug should be fixed in 1.18)
Is any way to install 1.17 again ?

[girish]

@vojtam can you reach out on support@cloudron.io ? I feel we miss something wrt your setup.

[nebulon]

To narrow down the issue a bit, can you install a surfer app instance and see if you can log in there? It uses mostly the same code for the log in session, so it should also fail.

[vojtam]

@nebulon - in Surfer App is same error like in meemo...

[nebulon]

So then this is not meemo related, but an OpenID provider issue on your Cloudron. To debug this further, can you send an email to support@cloudron.io ?

[vojtam]

@girish, @nebulon :
Thank you for your support, i Fixit ! a few day ago...
Just set up unbound in Cloudron server...
It was enough to add line:
to: /etc/unbound/unbound.conf.d/cloudron-network.conf : local-data: "<my.MYDOMAIN.COM> IN A x.x.x.x"
x.x.x.x is primary IP my server.