-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic Device Update Not Working #457
Comments
Sounds like a issue with the nginx configuration 🤔 Have you try reinstalling the add-on from scratch? |
this is the HA add-on Tasmoadmin yes i have uninstalled / re-installer the add-on as a whole works |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
I am on the latest version as previously noted |
I cant make automatic updates to work either I have tried to the OTA server IP to Unable to access OTA URL @ http://ota.tasmota.com/:80/data/firmwares/tasmota.bin.gz I have also tried my internal IP address 192.168.2.245 and then i get the error "http://192.168.2.245:9541/data/firmwares/tasmota-minimal.bin.gz" I dont how to make Automatic update to work when TasmoAdmin add "/data/firmwares" to the URL and this seems to be hardcoded? |
When you try to perform anAutomatic update.
You get an error with your IP adress as entered in OTA Server IP
Minimal Firmware is not accessible on the server at http://192.168.0.15:9541/data/firmwares/tasmota-minimal.bin.gz
Please check the OTA IP address and port are correct
Full Firmware is not accessible on the server at http://192.168.0.15:9541/data/firmwares/tasmota.bin.gz
Please check the OTA IP address and port are correct
If i try to access the exact address its going to, as listed above
http://192.168.0.15:9541/data/firmwares/tasmota-minimal.bin.gz
You get an nginx error 403 Forbiden
This has been an issue for about a year
It has previously worked for about 4 years
Only creating ticket now as there were existing ones but they seem to be gone
The text was updated successfully, but these errors were encountered: