Hi.
Thanks for your comment.
We have to revisit this tutorial.
Regards,
Sara

Then as application/json for a test JSON payload ({“value1″:”19″,”value2″:”67″,”value3″:”78”}).

Only the JSON payload is sent (https.POST(“{\”value1\”:\”19\”,\”value2\”:\”67\”,\”value3\”:\”78\”}”)), which doesn’t match the PHP script’s expectations. The PHP script expects application/x-www-form-urlencoded data with specific fields (api_key, Sensor, Station, Water_T, etc.).

The httpRequestData string, which contains the correct sensor data, is constructed but commented out and never sent.

Fix:
Remove the JSON test payload and send the httpRequestData with the correct Content-Type.

Update the POST request to use httpRequestData:

also with the Wifi method

WiFiClientSecure Misuse:
The code creates a new WiFiClientSecure object in the loop() function (WiFiClientSecure *client = new WiFiClientSecure;), which is unnecessary since a global client is already defined. This can lead to memory leaks or connection issues.

The global client is initialized in the global scope (WiFiClientSecure *client = new WiFiClientSecure;), but the loop() creates a new local instance, which shadows the global one.

Fix:
Remove the local client declaration in loop() and use the global client.

Move the setInsecure() call to setup() since it only needs to be set once.

Server URL and Network Issues:
The serverName is set to 192.**..***/post-Lake-Data.php, which is a local IP address. If the ESP32 and the server are not on the same network, or if the server is not reachable at this IP, the connection will fail, resulting in a -1 error.

The use of WiFiClientSecure with setInsecure() suggests the code is prepared for HTTPS, but the URL uses HTTP (192.**..***/post-Lake-Data.php). If the server expects HTTPS, this mismatch could cause a connection failure.

Fix:
Ensure the server is accessible at 192.**..*** from the ESP32’s network.

If the server uses HTTPS, update the URL to https://192.***.*.***/post-Lake-Data.php. If it’s HTTP, switch to WiFiClient instead of WiFiClientSecure:

I had the same problem, it’s because you may have chosen a root password in Maria Db that phpmyadmin decides is insecure. You need to reset the password to something more secure…. digitalstartup.co.uk/t/cannot-log-in-to-phpmyadmin-ubuntu-server/374

It says:
#1267 – Illegal mix of collations (utf8mb4_general_ci,COERCIBLE) and (utf8mb4_unicode_ci,COERCIBLE) for operation ‘<>’

And it would’nt go away :c