OmerAn
(Ömer Faruk ARAN)
October 15, 2021, 12:41am
1
Hello there;
I am getting the following error in the zigbee2mqtt log record installed on Home Assistant. The 172.30.33.3 ip address specified here does not belong to me, I use the ssl side with a dns record over my own domain name and the ssl side is completely healthy. My problem is how can I change my own domain name instead of 172.30.33.3 ip address in zigbee2mqtt module.
configuration:
data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: mqtts://localhost:8883
user: mqtt_user
password: '25278146'
serial:
port: /dev/ttyUSB0
disable_led: false
adapter: zstack
advanced:
log_level: debug
pan_id: 6754
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
rtscts: false
baudrate: 115200
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
host: 'domain'
experimental: {}
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: '-d -d'
log: true
Error:
21-10-15 03:37:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.3:8099 ssl:default [Connect call failed ('172.30.33.3', 8099)]
francisp
(Francis)
October 15, 2021, 5:40am
2
That is part of the docker network.
Why use and your own domain and ingress ? Choose one of the two.
OmerAn
(Ömer Faruk ARAN)
October 15, 2021, 6:27am
3
Because I can connect via ssl and use it with domain name in both local or remote connection. Thus, when the phone switches to wifi or cellular, there is no disconnection etc., it works more quickly.
This 172… ip is not accessible Could this 172… ip home assistant have a connection to the cloud?
I remember that when I made the first ssl settings, it was automatically redirected to this ip, then I overcame it with the following code in the configuration.yaml file.
homeassistant:
external_url: "https://domain.com:8123"
internal_url: "https://domain.com:8123"
legacy_templates: false
http:
base_url: "https://domain.com:8123"
francisp
(Francis)
October 15, 2021, 6:36am
4
If you use ingress, you connect to the zigbee2mqtt interface using the HA domain. No need for an extra domain.
OmerAn
(Ömer Faruk ARAN)
October 15, 2021, 6:53am
5
I made a fix but I still get the same error.
OmerAn
(Ömer Faruk ARAN)
October 15, 2021, 8:42am
6
Config file:
homeassistant:
external_url: "https://domain.com.tr:8123"
internal_url: "https://domain.com.tr:8123"
legacy_templates: false
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
http:
base_url: "https://domain.com.tr:8123"
server_port: 8123
ssl_certificate: /ssl/origin.pem
ssl_key: /ssl/privkey.pem
use_x_forwarded_for: true
trusted_proxies:
# Add the Cloudflare IPs as trusted proxies https://www.cloudflare.com/ips-v4
- 173.245.48.0/20
- 103.21.244.0/22
- 103.22.200.0/22
- 103.31.4.0/22
- 141.101.64.0/18
- 108.162.192.0/18
- 190.93.240.0/20
- 188.114.96.0/20
- 197.234.240.0/22
- 198.41.128.0/17
- 162.158.0.0/15
- 104.16.0.0/13
- 104.24.0.0/14
- 172.64.0.0/13
- 131.0.72.0/22
frontend:
themes: !include_dir_merge_named themes
media_player:
- platform: androidtv
host: 192.168.1.69
name: ARAN-IOT-TABLET
alarm_control_panel:
- platform: manual
name: home_alarm
code: !secret alarm_code
arming_time: 30
delay_time: 45
logger:
default: warning
logs:
custom_components.bosch: debug
bosch_thermostat_client: debug