After UTM update I can no longer login to my firewall nor ping external sites.

Does rebooting several times fix this?

When you say you have no backup, do you mean that your UTM's hard drive failed?

You are the first person ever to report this particular issue - please show us a picture of what you're seeing.

Cheers - Bob

nope... I've tried probably 6 or so times. 

The hard drive on my firewall did not fail. Just the drive where I had my backups stored. Didn't realize that's what was on the drive until today. I haven't done anything but update my firewall for the last 6 months or so which is why I never took a new backup. I get this error after I type in my credentials and try to login. Local login to the device using a keyboard also does not work.

I was more interested in the context than the message, Justin.

if you do an ls /var/confd/var/storage/snapshots/ at the command line, what do you see?

Cheers - Bob

how do i get a command line if I can't login? I'm not a pro with sophos.

If you attach a keyboard and a monitor to your UTM, Justin, you can check this at the console.  If you've never logged in at the command line and you haven't set the root password, you will have a chance to enter it the first time you login as root.  If you have already set the password for root and don't remember it, use Sophos UTM: How to recover access in the event of password loss.

Cheers - Bob

Use an ssh client to ssh to utm's ip address.  Assuming you've established a shell password, use "loginuser" (w/out quotes) as the user name.

You can also use "root" to login locally to the appliance/box running utm.

@Bob, how does one implement these snapshot files?

So I was able to get local root login. There are 39 snapshots. Being I'm doing this directly without putty/ssh I can't copy and paste all of them. Would take me hours to type. I will if needed... Dont troll me! :p I was able to use an old password to get into the root account so I didn't have to reset anything. 

So I was able to get local root login. There are 39 snapshots. Being I'm doing this directly without putty/ssh I can't copy and paste all of them. Would take me hours to type. I will if needed... Dont troll me! :p I was able to use an old password to get into the root account so I didn't have to reset anything. 

Google search on the path above led to this:

https://community.sophos.com/kb/en-us/119814

Steps on how to actually use these snapshots.

I've restored the 3 latest snapshots working from newest to oldest. All 3 from before the update. Did not correct the issue. 

You did make a backup of the entire system before updating?  Try restoring that.

If not, you can reinstall (from iso), the  old version, then restore a backup.  Make sure to save these snapshots somewhere before doing so because new install will wipe the drive.  You will also lose your accumulated log files. They are not part of the backup file.

Perhaps Bob has some other less destructive ideas¿?

I've been trying to figure out how to turn on ssh from the local access of the firewall but I can't figure it out. Every google search just ends up showing me how to do it in the gui.

Try the last commands in this post

https://community.sophos.com/products/unified-threat-management/f/hardware-installation-up2date-licensing/29960/astaro-7-webadmin-password-lost/99837#99837

So I was able to get ssh enabled but I can not login with 'loginuser' even after resetting it's password... I have given it quite a bit of time in case it was locked out. I also changed the password a couple times. Any idea on why it won't connect? I can get putty to connect and prompt for credentials but I can not get further than that. 

I finally got my firewall fixed. I reset the passwords again because I couldn't remember what I set it to the last time I was troubleshooting. 

https://community.sophos.com/kb/en-us/115346

I then updated the firewall from command line connected locally with a keyboard and mouse. "auisys.plx --verbose" is the command I used

https://community.sophos.com/kb/en-us/115382

After the update I was no longer having the error pop up when logging in. All is well. Thanks for the help guys!