|
|
#1 (permalink) |
|
Untangler
Join Date: Apr 2008
Location: New Orleans, La
Posts: 67
![]() |
Untangle upgraded last night to the new version, now I can't access the firewall via the web console. Any tips? It is going to be a PITA to unhook and pull down to connect to a monitor and keyboard/mouse... but if that is my only option then I can do it.
I'm getting time out message when attempting to connect via the web interface. |
|
|
|
|
#3 (permalink) |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 6,694
![]() |
I think he means the administration interface.
johndball? how do you know you've been upgraded? what version did you get upgraded to? what is your server's key/UID? (pm it to me) |
|
|
|
|
#4 (permalink) |
|
Untangler
Join Date: Apr 2008
Location: New Orleans, La
Posts: 67
![]() |
I'm on my Blackberry right now, sorry for any typos.
I wen to "Upgrade" last night and the box downloaded and installed the new 6.2? update and it no longer boots into the Untangle GUI. I'm in the hardware workaround right now looking at the verbose log and it looks like it is stuck at "parse error in file '/var/lib/dpkg/updates/0039' near line 17 package 'libplrpc-perl': EUP after field name' Starting UVM:................... And it sits there... this is the third retry and after 30 minutes still nothing.... |
|
|
|
|
#6 (permalink) |
|
Untangler
Join Date: Apr 2008
Location: New Orleans, La
Posts: 67
![]() |
I'm back on the network, however without Untangle as the router. It looks as if the box downloaded and installed Untangle 6.2... I really have no idea how it did this but that is what is currently partially running. I'm in the process of downgrading to 6.1 and probably will have to rebuild all the rules manually as I had no backup of the settings
![]() Oh well.... |
|
|
|
|
#7 (permalink) |
|
Untangle Junkie
![]() Join Date: Nov 2006
Location: San Mateo, CA
URLs submitted: 10
Posts: 6,694
![]() |
before you nuke that box - would you mind enabling remote support and PMing me your key/UID so we can look at the server?
is it still online? if so, I can probably see what happened and fix it. My guess is that it is file system corruption (that seems to be the cause of most dpkg errors), but if it has remote support on I can verify that. |
|
|
![]() |
| Thread Tools | |
|
|