# Influx Configuration Node - unexpected https:// protocol

**URL:** <https://discourse.nodered.org/t/influx-configuration-node-unexpected-https-protocol/85596>\
**Category:** General\
**Tags:** influxdb\
**Created:** [16 February 2024 16:00 UTC](https://discourse.nodered.org/t/influx-configuration-node-unexpected-https-protocol/85596 "2024-02-16T16:00:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ricm](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@ricm](https://discourse.nodered.org/u/ricm)\
**Post date:** [16 February 2024 16:00 UTC](https://discourse.nodered.org/t/influx-configuration-node-unexpected-https-protocol/85596/1 "2024-02-16T16:00:16Z")

</div>

Good afternoon,

I'm having problems configuring the Influx Configuration Node (i.e., the Influx Server selected when setting up an InfluxDB In or InfluxDB Out Node). I'm using InfluxDB v1.8

1. Occasionally the protocol defaults to `https://` even when "secure connection" checkbox is unchecked. The only way I've found of reverting to http: is to select "secure", deploy, then deselect it and deploy again. The JSON configuration node below has `http://` but also has a blank SSL/TLS node. It this correct/expected?

```auto
[
    {
        "id": "b644ba197cda86be",
        "type": "influxdb batch",
        "z": "4c457c4eb7ed6a80",
        "influxdb": "6ca8bde.9eb2f55",
        "precision": "",
        "retentionPolicy": "",
        "name": "Influx Out Batch (v1.x)",
        "database": "database",
        "precisionV18FluxV20": "ms",
        "retentionPolicyV18Flux": "",
        "org": "organisation",
        "bucket": "bucket",
        "x": 1100,
        "y": 480,
        "wires": []
    },
    {
        "id": "6ca8bde.9eb2f55",
        "type": "influxdb",
        "hostname": "172.20.0.2",
        "port": "8086",
        "protocol": "http",
        "database": "mydb",
        "name": "InfluxDB B1.x (172.x.x.x)",
        "usetls": false,
        "tls": "f7f39f4e.896ae",
        "influxdbVersion": "1.x",
        "url": "",
        "timeout": "",
        "rejectUnauthorized": false
    },
    {
        "id": "f7f39f4e.896ae",
        "type": "tls-config",
        "name": "local-tls",
        "cert": "",
        "key": "",
        "ca": "",
        "certname": "",
        "keyname": "",
        "caname": "",
        "verifyservercert": false
    }
]

```

I have found that I can export the node, edit it to `http://` if necessary and re-import it if `https://` persists.

1. The second problem occurs, again when configuring the Configuration Node. The port is consistently 8086 (and this is confirmed in Portainer), below:

`[influxdb] healthy iotstack [influxdb:1.8] 2024-02-07 07:36:43 172.20.0.2 [8086:8086] administrators`

As you can see it was installed via IOTstack using its defaults.

The issue concerns the host and port settings. I expected to be able to use any of:

```auto
[mylocalip_address] <-- (e.g., 192.168.1.100)
[hostname.local] <-- (e.g., myraspberrypi.local)
[localhost]

```

... but none of these will connect to InfluxDB. The only host that 'works' is:

`[172.20.0.2]`

... which is the IP address reported in Portainer, above, and which is, I assume(?), the IP address INSIDE the container that is eventually mapped to the local network IP address. That would be OK were it not for fact that a restart of the container results in a change of this IP address. I need something that endures.

NOTE: when accessing influxdb from Grafana, the followin g connection is successful

```auto
http://192.168.1.100:8086

```

I'm new to much of this and I'm now lost as to why, where to look and what to do.

Any and all help much appreciated,  
Ric

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [16 May 2024 16:00 UTC](https://discourse.nodered.org/t/influx-configuration-node-unexpected-https-protocol/85596/2 "2024-05-16T16:00:20Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.