Is see in the release notes there is a 1.0e and 1.0f release for control, but on docker hub I can only find the 1.0d tag
Any tips or clues as to when those images get updated?
Reason for asking is that I got everything setup on 1.0d but the account creation validation emails do not arrive nor do the password reset mails. So I cannot update from within the controller.
I have my controller behind nginx-proxy-manager. Maybe some port that needs to be opened up?
I do see some CORS errors since my domain is not manage.alta.inc
Hey there,
this seems to be a duplicate of
https://forum.alta.inc/t/local-controller-docker-upgrade
Hope this helps you out 
2 Likes
No not really since I have this installed behind a reverse proxy for which support is just now in 1.0f but since I cannot get into the controller at the moment I need the new version of the image so it can be configured correctly from the get go.
Also not using the macvlan docker network
unless I can force the update from the shell ?
So some additional attempts show that since I have this behind a reverse proxy with my own domain it won’t execute the api calls as they return “bad origin”"
At first there was an additional issue where my proxy would forward from https to http upstream which caused mixed content issues, then exposing the controller via http this went away.
But I never received the dyndns name for my controller and that is the missing glue at the moment.
Also I prefer the instructions not to use macvlan and also explain the needed ports since I am not hosting the controller locally in my network but offsite on a server with other containers.
I’m sorry, I started writing you last night, then I received 3 tornado warnings over 5 minutes via the emergency alert system, so I went offline and then forgot to come back and submit my reply.
Our current Docker container has persistence, it is not immutable. It’s just like a standard nix box, you can use apt to update the bundled packages so that it updates to 1.0f.
MAC VLAN is for automatic local discovery of the APs. Your Control instance is remote, so you don’t technically need that. If you still wish to do that, but without MAC VLAN, you could create a bridge. Issuing something like docker network create -d bridge --subnet=192.168.1.0/24 --gateway=192.168.1.1 AltaControl-Bridge would work, you would just need to replace the subnet w/ CIDR and gateway with the relevant info for your configuration.
The potential list of ports that you need to open are 80/tcp, 443/tcp, 53/udp, and 5353/udp.
All said, I’m not sure what you’ve done or undone trying to get it working on the unsupported version, so not fully sure what to suggest in that context. It probably would be simpler/quicker to just start with a fresh container and update via apt before touching anything else.
These new settings will be available under Settings>System>Advanced, once upgraded to 1.0f+:
Hope that helps as a start. Please let us know what other questions/concerns you may have, or if you run into other issues getting set up.
1 Like
I have tried several attempts I will try again with this information, I did try the apt update apt upgrade, but seemingly no alta packages where being updated. Am I missing something?
Ah, that’s because Alta is not in the name. The current package on our repo is access.
The following one-liner can verify that, if you wish: wget -O - https://dl.alta.inc/do-not-distribute/repo/dists/jammy/main/binary-amd64/Packages.gz | gunzip -c > Packages; grep -E '^Package:' Packages | awk '{print $2}'
Okay I got it working but it is very unstable behind the reverse proxy I get frequent bad gateway 503 while my other sites behind the proxy are doing just fine…
Gonna give up now and let you guys figure out this docker and reverse proxy stuff a bit more because since there is no support for volumes or external databases this makes the docker useless in my case.
I have tested the AP and the performance is awesome, but since the control and cloud is rather limited regarding detailed insights I will be returning the AP.
I’ll check you guys out again within a year or so.
Sorry to hear that, and also the late reply. This is a very new product, and development is far from over. We are very open and do listen to suggestions/feedback to improve our products to meet the demands of our customer base.
I’m going to reach out via email to discuss a few things, and we’d also love to get on a call sometime, obviously if you’re willing.