SSL Cert in RAK7249/RAK7258

[wwbusch (Wolfgang Busch)]

Hi guys,

any idea how to cheat the google chrome ssl problem with RAK HW? it always shows me “sorry you have invalid SSL cert on the device and sorry we dont allow you to connect there”.

Safari also complains and firefox in newest version does not allow to login.

Any idea?

Thanks
Wolf.

[Nicholas]

Could you take a screenshot to illustrate the problem you describe more clearly? So that we can better solve, thank you.

[rylRAE (Anthony E. Raterta)]

Hi @wwbusch

I believe your browser is prohibiting you on connecting to the specific address to access your RAK7258/RAK7249. For this, I am using Google Chrome. Kindly follow the steps:

1. Access the IP address of your RAK7258/RAK7249.
   
   
2. Click the “Advanced” Button and then click “Proceed to 192.168.1.3 (unsafe)”. Keep in mind that the IP Address may vary depending on your DHCP settings.
   
   
3. It should then display the homepage same with this:
   
   

Best regards,
Anthony

[wwbusch (Wolfgang Busch)]

Hi Anthony,

the problem in chrome 80 on OSX is, that it does not allow me to procceed unsafe.
No way.

I can only try to install the cert (dont know how) or use safari browser.

It should be possible in OpenWRT to change / install a ssl cert for this case…

Or disable SSL…

Wolf.
(sorry for the german text, can not switch chrome to english … )

[RAK_nuernberg (George)]

I have the same problem on RAK7249 with firefox.

[yutao]

Hi:
We have updated the certificate of the web server in the new version （1.1.0061_Release r199). Install the following certificate into the system’s Trusted Root Certificate store. When accessing the gateway (192.168.230.1) through Wi-Fi, the web console of the gateway is a trusted and secure site.

I am working on the certificate issue when accessing the gateway through other interfaces (Ethernet / LTE / OpenVPN etc).

https://downloads.rakwireless.com/en/LoRa/DIY-Gateway-RAK7249/Firmware/RAK7249_Latest_Firmware.zip

-----BEGIN CERTIFICATE-----

MIID8TCCAtmgAwIBAgIJAMiU+aTi1iBnMA0GCSqGSIb3DQEBCwUAMIGNMQswCQYD

VQQGEwJDTjESMBAGA1UECAwJR3VhbmdEb25nMREwDwYDVQQHDAhTaGVuemhlbjEM

MAoGA1UECgwDUkFLMQwwCgYDVQQLDANSJkQxGDAWBgNVBAMMD3Jha3dpcmVsZXNz

LmNvbTEhMB8GCSqGSIb3DQEJARYSY2FAcmFrd2lyZWxlc3MuY29tMCAXDTIwMDIx

NDAxMjMzOVoYDzIxMjAwMTIxMDEyMzM5WjCBjTELMAkGA1UEBhMCQ04xEjAQBgNV

BAgMCUd1YW5nRG9uZzERMA8GA1UEBwwIU2hlbnpoZW4xDDAKBgNVBAoMA1JBSzEM

MAoGA1UECwwDUiZEMRgwFgYDVQQDDA9yYWt3aXJlbGVzcy5jb20xITAfBgkqhkiG

9w0BCQEWEmNhQHJha3dpcmVsZXNzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP

ADCCAQoCggEBALzzdv9Il0oOMcfj/c3mxaohFKq9sRyMcJ8456VRdMsjYt36T8gQ

TAtYZzyWPoxqeXzskmHR1nEZAxo5HO3lZOrrEhbaDzTsaWfhiVroMpb0OYsIlPy0

a6HQEG2miGe2RMkbvtcCf3aes6RgBIYoHvOtF52aDnj6KnU+piykpf3xRWlLHMYQ

bR1RLSFE4Ta0x9w4EAN/bYug7p+2kgH63YVTGZgWMBGMrhPRWIP9SfeWyuGu9VYP

YH/P1PNBaFbcZjjhszP6nh4OArggETX14g76WqMFMj3T8NPRWw3MG8ulXw1GYRRZ

7Q0x3+wnacORlGH0KxJyS4DTqiPCD5g5oNECAwEAAaNQME4wHQYDVR0OBBYEFKgg

WDMhCR/z9FyDSf4jsyAUmEr/MB8GA1UdIwQYMBaAFKggWDMhCR/z9FyDSf4jsyAU

mEr/MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAKnMxkZqtEjFQ1qi

2essfXcpZCTzkh5JRc6SeQeZcVnAMZh+NXbHvk2T9HAIJBTcKY1Yrh7Qzd3T2utZ

0igHB1FQr/HR4TgIDpyqeTFjULzItp7UTVBsBNsMlTcaZOyNE32fpiAHOCLI6X7d

41AyMRZgQnMGk0/PQ/+Z9xBAr9eTGeWUCmC2Z2/mF8SfU5hPSbo977rPt6kbsPdX

xXaIL91SKNFzxfXDbMA6eCoHD7bhFqQXsoeLLiqrvOKwjGEEFYcMXF9sacoi1S64

LAcpDp9mI8gPQFrP8h91rbf+yf8VXlIVdElrOLN4iTpMBicGb3fVMlv+HTxRM4Qt

rgeuMUU=

-----END CERTIFICATE-----

[beegee (Bernd Giesecke)]

I am using LoRaGateway_1.1.0063_Release_r205 and the problem is still the same.

[silverio (Juan Fernando Semaan)]

I had the same issue on OSX with chrome. So I opened the keychain access, looked for that certificate and changed SSL to always trust. And now I can see the proceed link in chrome.