I experience the same error. After login I get “Unable to connect to Home Assistant.”. What should be the correct http: setup in configuration.yaml?
I completely started over with hassio yesterday, so my versions are:
-----------------------------------------------------------
Hass.io Add-on: Nginx Proxy Manager
Manage Nginx proxy hosts with a simple, powerful interface
-----------------------------------------------------------
Add-on version: 0.2.1
You are running the latest version of this add-on.
System: Ubuntu 18.04.3 LTS (armv7 / odroid-xu)
Home Assistant version: 0.99.3
Supervisor version: 189
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
I solved the problem on my system. When I initially setup Nginx proxy manager, I did forget to turn on “Websockets Support” in the proxy host configuration. After turning it on, everything is now working as expected.
First there are a few issues opened here https://github.com/jc21/nginx-proxy-manager concerning subfolder in URL.
Moreover, all the Letsencrypt SSL generation process needs the port 80 to be opened.
Hi,
Im trying to set the security headers such as x-frame-options and x-content-type-options etc. However, this code under advanced doesn’t seem to work.
I’ve got the add-on running fine but when I try logging in with Trusted Locations from clients that are on the allowed subnet it doesn’t work. I get the following error:
Hi @RobotGib, I’m experiencing similar issues to yours and @b.maia81. I have an TG-789 Broadband Gateway in bridge mode connected to my cable modem followed by an Apple TimeCapsule router. I’m just about to resort to replacing the TimeCapsule with an Ubiquiti EdgeRouter X apropos the pointers above.
Any additional hints you could give me on how you overcame the blockage would be gratefully received.
I do need help to be able to load my router page from my phone though. It always shows the desktop site, is there a way to deliver the mobile page? maybe by adding in a mobile user agent or something? I’ve tried the mobile address but it reverts back.
When I try the new proxied URL I’m just getting “unexpectedly dropped connection” on a vanilla Hassio install. Any ideas? From the slick video I expected this to “just work”
I’m using an existing DNS A record that I have pointed to my external IP for a while now.
Edit: Disregard this, @frenck rocks, my LAN sucks for not doing NAT loopback.
just posting here for visibility if someone else have this issue with the error Bad magic header in tc log. the add-on itself is working but I can’t access to web ui. here is the log:
[10:14:38] INFO: Starting MySQL database server...
2019-12-18 10:14:38 0 [Note] /usr/bin/mysqld (mysqld 10.3.20-MariaDB) starting as process 21762 ...
2019-12-18 10:14:38 0 [Note] InnoDB: Using Linux native AIO
2019-12-18 10:14:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-12-18 10:14:38 0 [Note] InnoDB: Uses event mutexes
2019-12-18 10:14:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-18 10:14:38 0 [Note] InnoDB: Number of pools: 1
2019-12-18 10:14:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-12-18 10:14:38 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-12-18 10:14:38 0 [Note] InnoDB: Completed initialization of buffer pool
2019-12-18 10:14:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-12-18 10:14:38 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-12-18 10:14:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-12-18 10:14:38 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-12-18 10:14:38 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-12-18 10:14:38 0 [Note] InnoDB: Waiting for purge to start
2019-12-18 10:14:38 0 [Note] InnoDB: 10.3.20 started; log sequence number 7674851; transaction id 18193
2019-12-18 10:14:38 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
2019-12-18 10:14:38 0 [Note] InnoDB: Buffer pool(s) load completed at 191218 10:14:38
2019-12-18 10:14:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-12-18 10:14:38 0 [Note] Recovering after a crash using tc.log
2019-12-18 10:14:38 0 [ERROR] Bad magic header in tc log
2019-12-18 10:14:38 0 [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}
2019-12-18 10:14:38 0 [ERROR] Can't init tc log
2019-12-18 10:14:38 0 [ERROR] Aborting
I don’t know if it is a final solution but deleting tc.log in /data/mysql folder worked so far
I have setup the addon and I can access it outside my local network using duckdns link but inside my local network I need to use the IP address to access it. Using duckdns link inside my local network doesn’t work.