home assistant nginx docker

To my understanding this was due to renewed certificate (by DuckDNS/Lets Encrypt add-on), but it looks like NGINX did not notice that and continued serving the old one. Very nice guide, thanks Bry! Webhooks not working / Issue in setup using DuckDNS, Let's Encrypt, NGINX, NGINX without Let's Encrypt/DuckDNS using personal domain and purchased cert, Installing remote access for the first time, Nginx reverse proxy issue with authentication, Independant Nginx server under Proxmox for Home Assistant and every other service with OVH subdomains, Fail2ban, unable to forward host_addr from nginx. No need to forward port 8123. If we make a request on port 80, it redirects to 443. It is recommended to input your e-mail in docker parameters so you receive expiration notices from Lets Encrypt in those circumstances. If you purchased your own domain, you can use https://letsencrypt.org to obtain a free, publicly trusted SSL certificate. Configure Origin Authenticated Pulls from Cloudflare on Nginx. By the way, the instructions worked great for me! Next thing I did is to configure the reverse proxy to handle different requests and verify/apply different security rules. Leaving this here for future reference. Networking Between Multiple Docker-Compose Projects. The second service is swag. The config below is the basic for home assistant and swag. Unable to access Home Assistant behind nginx reverse proxy. Do you know how I could get NGINX to notice the renewal so that this kind of situation would not happen again? Selecting it in this menu results in a service definition being added to: ~/IOTstack/docker-compose.yml. In a first draft, I started my write up with this observation, but removed it to keep things brief. Every service in docker container, So when i add HA container i add nginx host with subdomain in nginx-proxy container. Could anyone help me understand this problem. document.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() ); This site uses Akismet to reduce spam. Managed to get it to work after adding the additional http settings and additional Nginx proxy headers in step 9 on the original post. Note that Network mode is "host". The config you showed is probably the /ect/nginx/sites-available/XXX file. Can I run this in CRON task, say, once a month, so that it auto renews? So, this is obviously where we are telling Nginx to listen for HTTPS connections. Last pushed a month ago by pvizeli. Its pretty straight-forward: Note, youll need to make sure your DNS directs appropriately. After scouring the net, I found some information about adding proxy_hide_header Upgrade; in the nginx config which still didnt work. Once this is all setup the final thing left to do is run docker-compose restart and you should be up and running. Learn how your comment data is processed. Most of the time you are using the domain name anyways, but there are many cases where you have to use the local address instead. But yes it looks as if you can easily add in lots of stuff. I have had Duck DNS running for a couple years ago but recently (like a few weeks ago) came across this thread and installed NGINX. For TOKEN its the same process as before. Open source home automation that puts local control and privacy first. They provide a shell script for updating DNS with your current IP using the same token approach that the dns plugin for DNSimple that Certbot uses. I hope someone can help me with this. In other words you wi. This was the recommended way to set things up when I was first learning Home Assistant, and for over a year I have appreciated the simplicity of the setup. Once you've got everything configured, you can restart Home Assistant. After the DuckDNS Home Assistant add-on installation is completed. Note that the proxy does not intercept requests on port 8123. Importantly, I will explain in simple terms what a reverse proxy is, and what it is doing under the hood. Install the NGINX Home Assistant SSL proxy add-on from the Hass.io add-on store and configure it with your DuckDNS domain Open a browser and go to: https://mydomain.duckdns.org . One other thing is that to overcome the root file permission issue and avoid needing to run a chown, you can set the PUID and PGID environment variables to the non-root user of the machine, which will be generally 1000. It's an interesting project and all, but in my opinion the maintainer of it is not really up to the task. Click on the "Add-on Store" button. Change your duckdns info. The reverse proxy is a wrapper around home assistant that accepts web requests and routes them according to your configuration. By mounting the ssl/letsencrypt folder from the nginx proxy manager into a named volume, I managed to load the ssl files into home-assistant so it can read them. GitHub. I wanted to play a chime any time a door was opened, but there was a significant delay of up to 5 seconds. I think that may have removed the error but why? Both containers in same network In configuration.yaml: http: use_x_forwarded_for: true trusted . It will be used to enable machine-to-machine communication within my IoT network. Some Linux distributions (including CentOS and Fedora) will not have the /etc/nginx/sites-available/ directory. To install Nginx Proxy Manager, you need to go to "Settings > Add-ons". Followings Tims comments and advice I have updated the post to include host network. The main things to point out are: SUBDOMAINS=wildcard, VALIDATION=dns, and DNSPLUGIN=dnsimple. The main things to point out are: SUBDOMAINS=wildcard, VALIDATION=dns, and DNSPLUGIN=dnsimple. For errors 1 and 2 above I added 172.30.32.0/24 to the trusted proxies list in my HA config file. I used the default example that they provide in the documentation for the container and also this post with a few minor changes/additions. Also, any errors show in the homeassistant logs about a misconfigured proxy? You run home assistant and NGINX on docker? It becomes exponentially harder to manage all security vulnerabilities that might arise from old versions, etc. esphome. Turns out, for a reason far beyond my ability to troubleshoot, I cannot access any of my reverse proxy domain names from devices running iOS 14 on an external IP. This is indeed a bulky article. Not sure if you were able to resolve it, but I found a solution. Strict MIME type checking is enforced for module scripts per HTML spec.. I thought it had something to do with HassOS having upstream https:// and that I was setting up the reverse proxy wrong (Adding Websocket support didnt work). It gives me the warning that the ssl certificate is not good (because the cert is setup for my external url), but it works. I dont think your external IP should be trusted_proxy as traffic will no show as coming from there. The next and final requirement is: access to your router interface as we will do one quick port forward rule, but more on that later, because now we will continue with DuckDNS domain creation. When I try to access it via the subdomain, I am getting 400 Bad Request and the logs from the HASS Docker container prints: 2021-12-31 15:17:06 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a . This means my local home assistant doesnt need to worry about certs. For this tutorial you will need a working Home Assistant with Supervisor & Add-ons store. In the next dialog you will be presented with the contents of two certificates. But from outside of your network, this is all masked behind the proxy. but web page stack on url Your home IP is most likely dynamic and could change at anytime. Per the documentation: Certs are checked nightly and if expiration is within 30 days, renewal is attempted. Output will be 4 digits, which you need to add in these variables respectively. This will allow you to work with services like IFTTT. Blue Iris Streaming Profile. I have the proxy (local_host) set as a trusted proxy but I also use x_forwarded_for and so the real connecting IP address is exposed. Or you can use your home VPN if you have one! Also forward port 80 to your local IP port 80 if you want to access via http. Hello, this article will be a step-by-step tutorial of how to setup secure Home Assistant remote access using NGINX reverse proxy & DuckDNS. 19. Since then Ive spent a fair amount of time, DNSimple + Lets Encrypt + NGINX in Docker for Home Assistant. Digest. Finally, the Home Assistant core application is the central part of my setup. Setup a secure remote access to the Home Assistant; Ensure high availability and efficient integration with thousands of connected devices; Use flow-based UI to program automations and scenes, Build a solution around free and open-source tools, NodeRED and Mosquitto services are accessible only from a local network. Enabling this will set the Access-Control-Allow-Origin header to the Origin header if it is found in the list, and the Access-Control-Allow-Headers header to Origin, Accept, X-Requested-With, Content-type, Authorization.You must provide the exact Origin, i.e., https://www.home-assistant.io will allow requests from https://www.home . The great thing about pi is you can easily switch out the SD card instead of a test directory and give it a try; it shouldnt take long. At the end your Home Assistant DuckDNS Add-on configuration should look similar to the one below: Save the changes and start the Home Assistant DuckDNS Add-on from the, After the NGINX Home Assistant add-on installation is completed. I never had to play with the use_x_forwarded_for or trusted_proxies for the public IPs to show correctly, so I can actually see the IPs that have logged to my HA. Last pushed a month ago by pvizeli. Things seem to be working despite the errors: 1) connect() failed (111: Connection refused) while connecting to upstream, client: , server: .duckdns.org, request: GET /api/websocket HTTP/1.1, upstream: http://172.30.32.1:8123/api/websocket, host: .duckdns.org, 2) connect() failed (111: Connection refused) while connecting to upstream, client: , server: .duckdns.org, request: POST /api/webhook/ HTTP/2.0, upstream: http://172.30.32.1:8123/api/webhook/, host: .duckdns.org, 3) SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 104.152.52.237, server: 0.0.0.0:443. Id like to continue using Nginx Proxy Manager, because it is a great and easy to use tool. I am leaving this here if other people need an answer to this problem. At the very end, notice the location block. This probably doesnt matter much for many people, but its a small thing. Then finally youll need to change your.ip.here to be the internal IP of the machine hosting Home Assistant. Some quick googling confirmed my suspicion encrypting and decrypting every packet can be very taxing for low-powered hardware like Konnected's NodeMcu boards. Any chance you can share your complete nginx config (redacted). BTW there is no need to expose 80 port since you use VALIDATION=duckdns. https://downloads.openwrt.org/releases/19.07.3/packages/. Today we are going to see how to install Home Assistant and some complements on docker using a docker-compose file. The main things to note here : Below is the Docker Compose file. The ACCOUNT_ID I grabbed from the URL when logged into DNSimple. This configuration file and instructions will walk you through setting up Home Assistant over a secure connection. Im forwarding port 80,443 on my router to my Raspberry Pi running an NGINX reverse proxy (10.0.1.111). Its pretty much copy and paste from their example. Forward port 443 (external) to your Home Assistant local IP port 443 in order to access via https. And using the SSL certificate in folder NPM-12 (Same as linked to home assistant), with Force SSL on. hi, Begin by choosing 'Volumes' in the sidebar, then choose 'new volume'. Again iOS and certificates driving me nuts! If some of the abbreviations and acronyms that Im using are not so clear for you, download my free Smart Home Glossary which is available at https://automatelike.pro/glossary. It is more complex and you dont get the add-ons, but there are a lot more options. My domain is pointed to my local ISP address via CloudFlare (CloudFlare integration is setup to automatically update the records). If youre using NGINX on OpenWRT, make sure you move the root /www within the routers server directive. Naturally I thought it was just a mistake on my end but I finally read something about iOS causing issues way back in 16 and instead used my hotspot to try from my mac and voila, everything worked fine. SOLVED: After typing this post, I tried one more thing, and enabled Websockets Support in Nginx Proxy Manager, that solved the issue. Since docker creates some files as root, you will need your PUID & GUID; just use the Unix command id to find these. Click Create Certificate. I had previously followed an earlier (dehydrated) guide for remote access and it was complicated I then forwarded ports 80 and 443 to my home server. Fortunately, Duckdns (and most of DNS services) offers a HTTP API to periodically refresh the mapping between the DNS record and my IP address. Full video here https://youtu.be/G6IEc2XYzbc I fully agree. This guide has been migrated from our website and might be outdated. Hi Ive heard/read other instructions which also set up port forwarding for port 80 to make sure a browser will redirect an http request for the domain to https. Powered by Discourse, best viewed with JavaScript enabled, SOLVED: SSL with Home Assistant on docker & Nginx Proxy Manager. All you have to do is the following: DuckDNS domain is created, but can you share what is your favorite Dynamic DNS service? I have a problem with my router that means I cant use port forwarding on 443 (if I do, I lose the ability to use the routers admin interface). Before moving, Previously I wrote about setting up Home Assistant running in Docker along with Portainer to provide a GUI for management. But why is port 80 in there? This will down load the swag image, create the swag volume, unpack and set up the default configuration. Hi. It's an all-in-one solution that helps to easily setup an Nginx reverse proxy with a built-in certbot client. NGINX makes sure the subdomain goes to the right place. To get this token youll need to go to your DNSimple Account page and click the Automation tab on the left. Step 1 - Create the volume. Cleaner entity information dialogs The first new update that I want to talk about is Cleaner entity Read more, Is Assist on Apple devices possible? Is as simple as using some other port (maybe 8443) and using https://:8443 as my external address? Does this automatically renew the certificate and restart everything that need to be restarted, or does it require any manual handling? Obviously this will cause issues, and everything weve setup will break since that A record will no longer point to the correct place. In this post I will share how I set up an ASP.NET MVC 5 project as a SPA using Vue.js. That means, your installation type should be either Home Assistant OS or Home Assistant Supervised. It is a docker package called SWAG and it includes a sample home assistant configuration file that only need a few tweaks. Hello. The main things to point out are: URL=mydomain.duckdns.org and the external volumes mapping. This next server block looks more noisy, but we can pick out some elements that look familiar. If you do not own your own domain, you may generate a self-signed certificate. Home Assistant Core - Open source home automation that puts local control and privacy first. And my router can do that automatically .. but you can use any other service or develop your own script. https://home.tommass.tk/lovelace?auth_callbackk=1&code=896261d383c3474bk=1&code=896261d383c3474bxxxxxxxxxxxxxx, it cant open web socket for callback cause my nginx work on docker internal network with 172.xxx.xx.xx ip. Finally, use your browser to logon from outside your home need to be changed to your HA host This explains why port 80 is configured on the HA add-on config screen we are setting up the listening port so that nginx can redirect in case you omit the https protocol in your web request! If you go into the state change node and click on the entity field, you should now see a list of all your entities in Home-Assistant. If you aren't able to access port 8123 from your local network, then Nginx won't be able to either. docker pull homeassistant/aarch64-addon-nginx_proxy:latest. Do not forward port 8123. This will not work with IFTTT, but it will encrypt all of your Home Assistant traffic. Ill call out the key changes that I made. Finally, all requests on port 443 are proxied to 8123 internally. Again, we are listening for requests on the pre-configured domain name, but this time we are listening on port 443, the standard port for HTTPS. Look at the access and error logs, and try posting any errors. Yes, I have a dynamic IP addess and I refuse to pay some additional $$ to get a static IP from my ISP. On a Raspberry Pi, this would be: After installing, ensure that NGINX is not running. in. In this case, remove the default server {} block from the /etc/nginx/nginx.conf file and paste the contents from the bottom of the page in its place. I also then use the authenticated custom component so I can see every IP address that connects (with local IP addresses whitelisted). at first i create virtual machine and setup hassio on it We utilise the docker manifest for multi-platform awareness. Both containers in same network, Have access to main page but cant login with message. I tried installing hassio over Ubuntu, but ran into problems. If everything is connected correctly, you should see a green icon under the state change node. My setup enables: - Access Home Assistant with SSL from outside firewall through standard port and is routed to the home assistant on port 8123. In this section, I'll enter my domain name which is temenu.ga. It takes a some time to generate the certificates etc. For that, I'll open my File Editor add-on and I'll open the configuration.yaml file (of course, you . Restart of NGINX add-on solved the problem. Nginx is a wrapper around Home Assistant that intercepts web requests coming in on ports 80 and 443. Not sure about you, but I exposed mine with NGINX and didnt change anything under configuration.yaml HTTP section except IP ban and thresholds: As for in NGINX just basic configuration, its pretty much empty. Just remove the ports section to fix the error. I personally use cloudflare and need to direct each subdomain back toward the root url. Creating a DuckDNS is free and easy. This block tells Nginx to listen on port 80, the standard port for HTTP, for any requests to the %DOMAIN% variable (note that we configured this variable in Home Assistant to match our DuckDNS domain name). If doing this, proceed to step 7. The purpose of a reverse proxy setup in our case NGINX is to only encrypt the traffic for certain entry points, such as your DuckDNS domain name. Once this is all setup the final thing left to do is run docker-compose restart and you should be up and running. I then forwarded ports 80 and 443 to my home server. However if you update the config based on the post I linked above from @juan11perez to make everything work together you can have your cake and eat it too (use host network mode and get the swag/reverse proxy working), although it is a lot more complicated and more work. Leave everything else the same as above. That DNS config looks like this: Type | Name The first thing I did was add an A record with the actual domain (example-domain.com), and a wildcard subdomain (*.example-domain.com) to DNS and pointed it at my home ip. In host mode, home assistant is not running on the same docker network as swag/nginx. Let me explain. Then under API Tokens you'll click the new button, give it a name, and copy the . Looks like the proxy is not passing the content type headers correctly. LAN Local Loopback (or similar) if you have it. swag | [services.d] starting services Hit update, close the window and deploy. Note that Network mode is host. Although I wrote this procedure for Home Assistant, you can use it for any generic deployment where you need to implement automatic renew of your certificates using the certbot webroot plugin.. nginx is in old host on docker contaner Home Assistant 2023.3 is a relatively small release, but still it is an interesting one. Also, we need to keep our ip address in duckdns uptodate. So instead, the single NGINX endpoint is all I really have to worry about for security attacks from the outside. In my configuration.yaml I have the following setup: I get no errors in the home assistant log. Letsinstall that Home Assistant NGINX add-on: if(typeof ez_ad_units != 'undefined'){ez_ad_units.push([[300,250],'peyanski_com-large-leaderboard-2','ezslot_9',109,'0','0'])};__ez_fad_position('div-gpt-ad-peyanski_com-large-leaderboard-2-0');When using a reverse proxy, you will need to enable the use_x_forwarded_for and trusted_proxies options in your Home Assistant configuration. I use Linux SWAG (Secure Web Application Gateway) from linuxserver.io as a reverse proxy. If this is true, you can use a Dynamic DNS service (like duckdns) to obtain a domain and set it up to update with you IP. Proceed to click 'Create the volume'. Get a domain . Im pretty sure you can use the same one generated previously, but I chose to generate a new one. The first thing I did was add an A record with the actual domain (example-domain.com), and a wildcard subdomain (*.example-domain.com) to DNS and pointed it at my home ip. docker-compose.yml. HA on RPI only accessible through IPv6 access through reverse proxy with IPv4, [Guide] [Hassbian] own Domain / free 15 Year cloudflare wildcard cert & 1 file Nginx Reverse Proxy Set Up, Home Assistant bans docker IP instead of remote client IP, Help with docker Nginx proxy manager, invalid auth. @home_assistant #HomeAssistant #SmartHomeTech #ld2410. Going into this project, I had the following requirements: After some research and many POCs, I finally came with the following design. Can I somehow use the nginx add on to also listen to another port and forward it to another APP / IP than home assistant. Digest. Powered by Discourse, best viewed with JavaScript enabled, Having problems setting up NGINX Home Assistant SSL proxy add-on, Unable to connect to Home Assistant from outside after update. I let you know my configuration to setup the reverse proxy (nginx) as a front with SSL for Home Assistant. Im pretty sure you can use the same one generated previously, but I chose to generate a new one. Internally, Nginx is accessing HA in the same way you would from your local network. Still working to try and get nginx working properly for local lan. Setup nginx, letsencrypt for improved security. It defines the different services included in the design(HA and satellites). Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. Those go straight through to Home Assistant. Go to the. But first, Lets clear what a reverse proxy is? I ditched my Digital Ocean droplet and started researching how to do this in Docker on my home server. Under this configuration, all connections must be https or they will be rejected by the web server. Excellent work, much simpler than my previous setup without docker! Digest. Check out home-assistant.io for a demo, installation instructions , tutorials and documentation. To get this token you'll need to go to your DNSimple Account page and click the Automation tab on the left. As a fair warning, this file will take a while to generate. Node-RED is a web editor that makes it easy to wire together flows using the wide range of nodes in the palette that can be deployed to its runtime in a single click. They all vary in complexity and at times get a bit confusing. The utilimate goal is to have an automated free SSL certificate generation and renewal process. Hass for me is just a shortcut for home-assistant. The final step of the Home Assistant Remote Access using NGINX Reverse Proxy & DuckDNS is to do some port forwarding in your home router. This same config needs to be in this directory to be enabled. Yes, I am using this docker image in Ubuntu which already contains the database compared to the official one: Docker container for Nginx Proxy Manager. It has a lot of really strange bugs that become apparent when you have many hosts. I am running Home Assistant 0.110.7 (Going to update after I have . #ld2410b #homeassistant #mmwave, Set up human presence detection with mmWave LD2410B sensor and Home Assistant in minutes Check out Google for this. My objective is to give a beginners guide of what works for me. ; mosquitto, a well known open source mqtt broker. Once I got that script sorted out, I needed a way to get it to run regularly to make sure the IP was up to date. NordVPN is my friend here. NodeRED application is accessible only from the LAN. It was a complete nightmare, but after many many hours or days I was able to get it working. There was one requirement, which was I need a container that supported the DNSimple DNS plugin since I host my sites through DNSimple. and I'll change the Cloudflare tunnel name to let's say My HA.I'll click Save.. I'm ready to start the Cloudflare add-on in Home Assistant, but before that, I have to add some YAML code to my configuration.yaml file. If you already have SSL set up on Home Assistant, the first step is to disable SSL so that you can do everything with unencrypted http on port 8123. Again, mostly related to point #2, but even if you only ran Home Assistant as the only web service, the only thing someone can find out about my exposed port is that Im running NGINX. How to setup Netatmo integration using webhooks to speed up device status update response times, WebRTC support for Camera (stream) Components, No NAT loopback / DuckDNS / NGINX / AdGuard, Websocket Connection Failed Through Nginx Proxy, Failed to login through LAN to HA while Internet was down (DuckDNS being used), External URL with subdirectory doesn't work behind nginx reverse proxy, Sharing Letsencrypt certificates between Synology and HA on docker, ChromeCast with NatLoopback disable router. I installed curl so that the script could execute the command. inner vlan routing, Remote access doesn't work with nginx reverse proxy, Router Port Forwarding XXXXX (custom port) to server running Nginx, Nginx collects custom port and redirects to HTTP 8123 on HASS running in Docker. You have remote access to home assistant. My ssl certs are only handled for external connections. Using NGINX as a proxy for Home Assistant allows you to serve Home Assistant securely over standard ports. The next lines (last two lines below) are optional, but highly recommended. I wouldnt consider it a pro for this application. Last pushed 3 months ago by pvizeli. Can any body tell me how can I use Asterisk/FreePBX and HA at the same time with NGINX. e.g. OS/ARCH. if(typeof ez_ad_units != 'undefined'){ez_ad_units.push([[300,250],'peyanski_com-large-mobile-banner-2','ezslot_14',111,'0','0'])};__ez_fad_position('div-gpt-ad-peyanski_com-large-mobile-banner-2-0');The port forwarding rule should do the following: Forward any 443 port income traffic towards your Router WAN IP (Or DuckDNS domain) to port 443 of your local IP where Home Assistant is installed. Scanned Add the following to you home assistant config.yaml ( /home/user/test/volumes/hass/configuration.yaml). The Home Assistant Community Forum. The best of all it is all totally free. homeassistant.subdomain.conf, Note: It is found in /home/user/test/volumes/swag/nginx/proxy-confs/. | MY SERVER ADMINISTRATION EXPERTISE INCLUDES:Linux (Red Hat, Centos, Ubuntu . I do not care about crashing the system cause I have a nightly images and on top a daily HA backup so that I can back on track easily if I ever crash my system. Go watch that Webinar and you will become a Home Assistant installation type expert. Your home IP is most likely dynamic and could change at anytime. This was super helpful, thank you! Vulnerabilities. client is in the Internet. Home Assistant is still available without using the NGINX proxy. This is in addition to what the directions show above which is to include 172.30.33.0/24. That doesnt seem possible with hass.io, and anyone trying to install any of the other supervised versions on linux always seems to have problems. Then copy somewhere safe the generated token. Optionally, I added another public IP address to be able to access to my HA app using my phone when Im outside. There was one requirement, which was I need a container that supported the DNSimple DNS plugin since I host my sites through DNSimple. DNSimple provides an easy solution to this problem. To get this token youll need to go to your DNSimple Account page and click the Automation tab on the left. If you dont know how to do it type in YouTube the following: Below is a screen of how I configured this port forwarding rule in Unifi Dream Machine router. Note that the ports statment in the docker-compose file is unnecessary since home assistant is running in host network mode. ZONE_ID is obviously the domain being updated. Go to the Configuration tab of the add-on and add your DuckDNS domain next to the domain section and Save the changes. Instead of example.com, use your domain. Page could not load. Effectively, this means if you navigate to http://foobar.duckdns.org/, you will automatically be redirected to https://foobar.duckdns.org/. Is it advisable to follow this as well or can it cause other issues? I have setup the subdomain and when I try to access it via a web browser I get a 400 error, when I try to connect the iOS app it says 400 error Shared.WebhookError 2. SOLVED: After typing this post, I tried one more thing, and enabled Websockets Support in Nginx Proxy Manager, that solved the issue. mizzou volleyball camp 2022, unit 3 progress check: mcq part a ap physics,

James Hill Obituary Hailey Idaho, Tytler Cycle Explained, Is Sending A Paypal Invoice Safe For Seller, Articles H