Hello @alexbelgium . Thank you for your work. I have one question. I use your mealie add-on and it work’s quite well. Could you add ingress support for the mealie instance? Could this easily be done by me if I only have to change some configs?
That would be way easier than for me to mess with SSL files and trying to install duckdns for an add-on next to the nabu casa.
Hi, ingress is super hard to implement and the biggest issue is that Mealie requires a hardcoded url at container creation which is not compatible with the way ingress works.
Should be good now - I’ll keep on v2.0 from now on. But make a full HA backup just to be sure! The database from your version is located in the /config of homeassistant, which is not backuped when doing the add-on back-up.
Once the Mealie mess is sorted and people have safely migrated to the new version, I’m implement the new logic for config storage that will allow to have it backuped with the addon
Hi, here is the initial thread discussing the lack of support for subpaths as ingress needs: Alexbelgium repo : 90+ addons - #332 by kenobrandt. BTW, several official add-ons also don’t support ingress (like bitwarden) in the end it is quite a hack…
If you find a way though I’ll be more than happy to implement it
Hi, honestly I have already way too many addons and prefer focusing on maintenance, except for things that I would myself use and especially given there is already strong addons for reverse proxies such as Nginx supported by HA itself. However you could use the portainer addon to run it
Hi @alexbelgium, I’ve been using quite a lot of add-ons from your repo, so I’d like to start with a big thanks!
I do have a problem with the Spotweb add-on though. It seems to install well, following the documentation and installing MariaDB as well. It starts fine, only outputting this error:
mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not support it
Error : /etc/cont-init.d/90-spotweb exiting 1
The webUI shows the database not existing:
Unable to connect to database:
SQLSTATE[HY000] [1049] Unknown database 'spotweb'
Please make sure your database server is up and running and your connection parameters are set
When I do create the database manually (using database name “spotweb”) it gives the following message:
2025/01/05 09:57:50 [error] 417#417: *11 FastCGI sent in stderr: "PHP message: SpotWeb Exception occured: 42S02: 1146: Table 'spotweb.settings' doesn't exist" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.136:8123"
And the webUI shows this message (similar to the one above):
after a long time running whitout issues do I have a issue now:
/etc/cont-init.d/90-spotweb: line 95: /usr/bin/maria: No such file or directory
cont-init: info: /etc/cont-init.d/90-spotweb exited 127
not starting anymore. my database is an external mariadb database on another machine. It always worked but not now. I don’t know how to fixx to be honest.
My mistake I wrote “maria” instead of mariadb based on this line mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead ; I’ve pushed a new version now