FCM with RTDB

[majo551]

I tested a project where I combine FCM and RTDB at once.
All worked fine , Oath2 .0 token generated fine, I was able to send the FCM messages, save values to RTDB and receive Stream (changes ) in a node.
However as of today afternoon the project stopped working on ESP32.
I see the the OATH2.0 token generated, I still can send the messages but I stopped being able to save data to RTDB and Stream times out 99% of the time.
When I save to RTDB I get a message

[127115][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -1
after which the save attempt ends with error : connection refused

Then next error related to stream follows:

[274347][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -1
stream begin error, connection refused

stream timed out, resuming...

error code: -3, reason: not connected

[276678][E][ssl_client.cpp:37] _handle_error(): [data_to_read():361]: (-29184) SSL - An invalid SSL record was received
[276679][E][ssl_client.cpp:37] _handle_error(): [data_to_read():361]: (-29184) SSL - An invalid SSL record was received

Suddenly the stream connects and then it gets the changed data, but immediately times out

stream timed out, resuming...

[397184][E][ssl_client.cpp:37] _handle_error(): [data_to_read():361]: (-76) UNKNOWN ERROR CODE (004C)

Strange thing is that all worked for last 2 weeks , errors started just today.

When I compiled the same to esp8266 env, everting (still) works as before with no error.

I need the project to run on ESP32 due to memory limits of 8266 and the speed.

Was there any change in Firebase today , affecting only ESP32 ? Is this a bug?

[mobizt]

Library works fine. The problem is your network.

[majo551]

Can you please be more specific, what to do with the network? The same code in the same network in different env behaves differently. Esp 8266 works with no error, esp32 ends with connection refused just for RTDB. And interesting fact is that all worked for both untill today....No changes in the code nor network. Ssl client unknown error in esp32 version.

[mobizt]

You should check that your hardware in network is functioning properly e.g. reset WiFi router, change your router, check your power supply, and change your ESP device.

[mobizt]

You should see that why your ESP8266 device works unless ESP32 as it runs on the same library source file.

I test my library almost 24/7 as many users request me to help on various support channels.

[mobizt]

Library works for all supported devices under the same code.

[mobizt]

Library updates can't be affected to your device anyway because I'm not a service provider or own or able to access your Firebase project.

And your device is already run the compiled binary code or firmware and it's impossible that the library changes can affected your device if you don't recompile and upload it.