Turris Omnia Out of Box Issues Cant do anything

  1. unbox omnia
  2. go through set up
  3. choose a few updater options like open vpn and nextcloud
  4. tells me to reboot
  5. gets in infinite circle that reads “trying to reboot”
  6. have to manual reboot
  7. try to go back to interface at 192.168.1.1 “500 internal service error”

I would just like to use my router and be able to access it after an update

this thing has been nothing but problems right out of the box. No Openvpn client, cant even update without this boot loop internal service error…what the heck?

1 Like

Maybe you should calm down a bit. Based on your multiple posts in this forum within a short period of time it seems like you are a beginner and lack some basic knowledge about Linux, OpenWRT and networking in general. This is totally fine, everybody starts at some point, but you should reconsider your general approach.

Did you find the Turris docs located here?
https://docs.turris.cz/
There you can find instructions on how to update your router, how to install some software and how to recover from failure. There even is a section about „Getting help“ that you should read carefully: https://docs.turris.cz/basics/support/

Take some time and get to know your device. If you have some specific questions this forum is the right place to ask them and there are many community members willing to help. But spamming multiple threads with imprecise questions and accusations is not the way to go… Ask precise questions and describe your problem as exactly as you can.

What software version is running on your Omnia? Maybe you should update to the latest version (4.0.3) before adding software.

2 Likes

Very sorry , noob rage fail, ill be more respectful

looked through the docs while.troubleshooting

Yes i ran the full setup wizard and updated to latest version but often ran into a " attempt to reboot after install - boot loop" and i would have to manually reboot on the turris (1 led reset).

Just want to put wan into.it and get lan out of it easily, maybe even run my very own vpn config file via the gui and route who gets what connection

Okay, so this is strange. Are you sure you waited long enough? Rebooting the Omnia is something I expect to „just work“…

Turris MOX has some reboot problems that are beeing investigated by Turris team at the moment but the omnia should reboot just fine.

Maybe you could try to reflash your router with latest firmware, while resetting it to factory settings always goes back to the software version the router was shipped with, this brings you to latest firmware. See section „Re-flash router“ here: https://docs.turris.cz/hw/omnia/rescue_modes/

If this doesn‘t help so that your omnia reboots at least it may be some hardware failure, so it might be helpful to contact support then… (See link „Getting help“ above)

Do you mean you want some clients route through vpn and some not? If yes, search this forum for „policy based routing“ but be warned that this topic is quite advanced…

Try setting it up initially without update options may succeed, then reboot and take it from there.

TOS provides a feature schnapps through which the user can create a snapshot for a working configuration and rollback to it if something goes awry later on, thus not necessarily having to start from scratch all over again.
That said it is not a silver bullet.

Currently schnapps is accessible only via ssh but not Foris and being a feature implemented by TOS it is not available via LuCI either.


That seems a bug of sorts indeed, also

is somewhat odd.

Had similar if not the same user experience like you with my Turris MOX. And I am doing Linux, OpenWRT, and networking for over a decade. Go figure! Especially that 500 error forced my to use one of the rescue modes as I did not enable the shell.

In other words, there is an issue, perhaps a software bug which needs to be tracked down. If you are able to reproduce your issue, would be interesting to get your

  1. Turris OS version, and
  2. all of your selected options in the configuration wizard, and
  3. the model/version of your upstream router, and/or
  4. the name/location of your Internet Service Provider (ISP).

Yes, that is work. I was not able to track down my issue, because I was not able to reproduce it, yet.

Did some factory resets and just did updates one at a time and that seemed to fix the software boot loop issue. however, after getting openvpn working finally, i now have a shiny new issue :

Getting 500 internal server error when trying to log into Foris

Luci login works, Lan Internet works, Openvpn works , ssh works

On current version of everything

Sorry pepe, im trying over here!

  1. turris version 4.0.3
  2. are you asking about foris wizard options ? if so, did not install anything other than extra luci options
  3. no upstream router just modem
  4. would rather not say

when i go to 192.168.1.1 it gives me the option of foris or luci, luci works, foris gives 500 internal service error, reboot did not fix

Yes, especially your DNS (and therefore for your upstream stuff). However, because you are on Turris OS 4.0.3, it sounds like the auto-updating worked, and then DNS should work as well. In my case, the defaults on the DNS pane did not work and then in the end I lost Foris. I had to go not for my ISP but another option like Cloudflare. Anyway, if Foris gives 500, I am not aware of any other solution than going for rescue mode 6. Perhaps somebody else knows a better approach.

really hoping for a solution that does not require yet another reset. Luci works great, openvpn even working but 192.168.1.1 and clicking foris still pushes 500 internal service error

Someone mentioned something about a command lighttpd ? can anyone shed some light on other things i can do ?

thanks