SSL/TLS Https doesn't work

Third Party Coronium
#1

Greetings everyone,

I am using Coronium Core 2.7.

Recently I changed Http to Https, but all methods are invalid.

First, I used the method provided by the document and returned a successful screen, but there was no response when I changed to Https.

In addition, I used the DigitalOcean method and the result was the same.

Finally, after I used Cloud flare, I successfully changed webmin to Https, but Coronium was also unavailable.

core.init({
	server = "https://mycore.mycoredonmain.xyz"
})

After this setting, I keep receiving “Timed out” responses.

core.init({
	server = "https://mycore.mycoredonmain.xyz/"
})

After this setting, I received Error code “1” response.

This problem has troubled me for more than a week, any comments are greatly appreciated.

Please give me some opinions, thank you.

The actual domain is hidden, please let me know if you need to it, thank you.

#2

I don’t know much about Coronium, but I’m curious are you having issue on the device or in the simulator? Older iOS and Android devices had an SSL cert expired a few weeks back, and it prevents accessing any HTTPS sites on the device. I believe it’s iOS 9 or before.

#3

Thanks for your response.

I currently only test on the simulator.

I follow @Develephant videos,but my https setting keeps encountering Timed out.

According to the video, there is no need to set “/”.

Not sure if the Api level of build.setting will affect.

I am very worried that if I use the ipv4 address directly, Google will not let me pass…

After all, coronium only makes more frequent interactive data, and there is no important data.

#4

Hi, everyone.

I finally searched almost all the files in the virtual machine and checked it, and found a solution, and shared it with everyone in need.

Configure your coronium.server.conf, add the things you need for port 443 under port 10001.

server {
	listen 10001;
    listen 443 ssl;
    server_name  ****.com;

	ssl	on;
	ssl_certificate /home/****.com.crt;
	ssl_certificate_key /home/****.com.key;

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
	ssl_prefer_server_ciphers on;
	ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

    ssl_session_cache    shared:SSL:1m;
	ssl_session_timeout  5m;

    include /usr/local/coronium/conf/coronium.locations.conf; 
	include /usr/local/coronium/conf/coronium.errors.conf;
}

You can place your key and crt anywhere. Then if you want to avoid port 80 being directly logged in, use rewrite to point to your domain.

This question took me a whole week, looking for various answers, really sad it…

And in the end I also knew why webmin works but solar2d does not, because I did not listen port 10001 under port 443.

Hope this answer can help all those in need.

1 Like