Pimatic service crashing with HTTPS enabled

---

Hello all,

I’ve an issue with my pimatic setup.
Started messing around with https instead of http connectivity but in some way the Pimatic service is crashing right after startup is finished.
Then, pimatic is starting all over again as you can see…
Anyone have a clue why this is happening?

21:39:30.698 [pimatic-mobile-frontend] info: packing static assets
21:39:32.965 [pimatic-mobile-frontend] info: packing static assets finished
21:39:32.980 [pimatic-mobile-frontend] info: rendering html
21:39:41.561 [pimatic-homeduino] debug: data: "ready"
21:39:41.720 [pimatic-homeduino] info: Connected to homeduino device.
21:39:41.761 [pimatic-homeduino] debug: data: "PING"
21:39:55.468 [pimatic-homeduino] debug: data: "ACK"
21:39:55.496 [pimatic-mobile-frontend] info: rendering html finished
21:39:55.619 [pimatic-homeduino] debug: Receiving on pin 0
21:39:55.623 [pimatic] info: Listening for HTTPS-request on port 443...
21:40:31.416 [pimatic] info: Flushing database to disk, please wait...
21:40:31.476 [pimatic] info: Flushing database to disk, please wait... Done.
21:40:31.480 [pimatic] info: exiting...
21:40:35.752 2018-04-15 Sunday

@marvandorth probably a mistake in your config. If you could post the https part, we can help you better.

@gleno0h

{
  "settings": {
    "debug": true,
    "logLevel": "debug",
    "httpServer": {
      "enabled": true,
      "port": 80
    },
    "database": {
      "deviceAttributeLogging": [
        {
          "deviceId": "*",
          "attributeName": "*",
          "type": "*",
          "interval": "0",
          "expire": "7d"
        },
        {
          "deviceId": "*",
          "attributeName": "*",
          "type": "continuous",
          "interval": "5min",
          "expire": "7d"
        },
        {
          "deviceId": "*",
          "attributeName": "temperature",
          "type": "number",
          "expire": "1y"
        },
        {
          "deviceId": "*",
          "attributeName": "humidity",
          "type": "number",
          "expire": "1y"
        }
      ],
      "messageLogging": [
        {
          "level": "*",
          "tags": [],
          "expire": "7d"
        },
        {
          "level": "debug",
          "tags": [],
          "expire": "0"
        }
      ]
    },
    "authentication": {
      "secret": "xxxxxxxxxx"
    },
    "httpsServer": {
      "enabled": true,
      "port": 443,
      "hostname": "",
      "keyFile": "ca/pimatic-ssl/private/privkey.pem",
      "certFile": "ca/pimatic-ssl/public/cert.pem",
      "rootCertFile": "ca/certs/cacert.crt"
    },
    "cors": {},
    "gui": {}
  },

i also tried https with the same result. Isnt it that you need to remove the http part? just a wild guess.

@countjuh shouldnt be an issur but worth a try. Strange that there isnt any debug info…

“If you want to use pimatic over the internet you should always use a SSL-Connection (https) for security reasons. You can configure pimatic to run just the http- or https-Server or both. By default only the (insecure) http server is enabled.”

@gleno0h

i know. but unfortunately i never been able to get it working
i use the http over internet. i stopped trying. not good. maybe you can give me a start so i can try?

Maybe access rights on the SSL files?

Mine is working ok with this config

  "settings": {
    "httpServer": {
      "enabled": true,
      "port": 80
    },
    "database": {
      "deviceAttributeLogging": [
        {
          "deviceId": "*",
          "attributeName": "*",
          "type": "*",
          "interval": "0",
          "expire": "7d"
        },
        {
          "deviceId": "*",
          "attributeName": "*",
          "type": "continuous",
          "interval": "5min",
          "expire": "7d"
        },
        {
          "deviceId": "*",
          "attributeName": "temperature",
          "type": "number",
          "expire": "7d"
        }
      ],
      "messageLogging": [
        {
          "level": "*",
          "tags": [],
          "expire": "7d"
        },
        {
          "level": "debug",
          "tags": [],
          "expire": "0"
        }
      ]
    },
    "authentication": {
      "secret": "xxxxxxxxxx"
    },
    "httpsServer": {
      "enabled": true,
      "keyFile": "/home/pi/certificates/SSLprivatekey.key",
      "certFile": "/home/pi/certificates/SSLcertificate.crt"
    },
    "gui": {},
    "cors": {}
  },

Maybe remove the empty "hostname": "",

@marvandorth @countjuh what does netstat -lptn | grep 443 say when pimatic isnt running?

Hostname “” should be the ip of your raspberry pi.

The weird thing is; whenever I enable both the HTTP and the HTTPS server it’s going perfectly fine?!
But I want to disable the unsafe option
@incmve Your certs are located in a different folder than mine.
Anyone an idea where these certificates go when generated during setup?

@gleno0h said in Pimatic service crashing with HTTPS enabled:

netstat -lptn | grep 443

I’ve tried your command to no avail.
After 3 tries of typing the whole RasPi crashes and reboots?!
This is starting to get weird.

@gleno0h

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp6 0 0 :::443 :::* LISTEN -

this is the result of the grep

I’d recommend using nginx as a reverse proxy and get https with letsencrypt certificates…

@countjuh if you did that, like i said, with pimatic turned off, it would mean that the ssl port is in use by another app. You can see the app with this command;

sudo netstat -tlnpu | grep 443

@marvandorth thats very strange, maybe you look at the system logs to get a clue?

@countjuh said in Pimatic service crashing with HTTPS enabled:

@gleno0h

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp6 0 0 :::443 :::* LISTEN -

this is the result of the grep

Should is not show 127 0.0.0.1:443 (localhost)?

@v1per ports are reserved for any (0.0.0.0) service. So the first service to occupy, gets the port. And in which 0.0.0.0 means “every host”

Node, for example, also listens to 0.0.0.0:80.
I think @countjuh has a service running on 443, while pimatic is off, so there would be an port issue which should be noted in the debug.

I am also having the same issue.
Whenever I include httsServer in the config file pimatic does not start and gives the following error
"[pimatic] Startup error: Error: PRAGMA synchronous=NORMAL; - SQLITE_IOERR: disk I/O error"

I have checked for use of port 443 and also changed the port but pimatic crashes when httpsServer is updated. if I remove httpsServer it all works fine.
Any help will be appreciated.

"httpServer":{
    "enabled": true,
    "port":8080
    },
    "httpsServer": {
    "enabled": true,
    "port": 500,
    "hostname": "",
    "keyFile": "ca/pimatic-ssl/private/privkey.pem",
    "certFile": "ca/pimatic-ssl/public/cert.pem",
    "rootCertFile": "ca/certs/cacert.crt"
    },

Please see the following topic for future posts containing code or command snippets. Thanks!
https://forum.pimatic.org/topic/1179/how-to-post-code-snippets-and-alike-on-the-forum

@rnavanee first, fix your database because that is corrupt;

https://forum.pimatic.org/topic/14/database-tips

@gleno0h I am not sure if the database is corrupt as I get the error only when the httpsServer section is introduced. I do not get the database corrupt error otherwise.

@countjuh said in Pimatic service crashing with HTTPS enabled:

@gleno0h

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp6 0 0 :::443 :::* LISTEN -

this is the result of the grep

@Gleno0h
You are correct. Nginx is running
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 894/nginx -g daemon
tcp6 0 0 :::443 :::* LISTEN 894/nginx -g daemon