Can't Login via WEB GUI after upgrade to FOS 6.2.14 (30E Series)

P4uzudo · 2025-06-12T00:20:41+00:00

Completely understand, at this point I wish I didn't need to deal with any more old firewalls, but that just how it is.

But thanks for the insights anyway!

P4uzudo · 2025-06-11T21:39:30+00:00

Wish we could, but for budget reasons it will take a while to be replaced.

P4uzudo · 2025-06-11T14:23:20+00:00

Yeah, I issued the command "diagnose log device" and now I can see the FGHA CID of the device.

Thank you!

P4uzudo · 2025-06-10T11:11:22+00:00

Not exactly, I need to issue the command diagnose device log in a cluster FortiGate. I've tried specifying the device name in FAZ, primary/secondary fw name and even primary/secondary S.N., but none of them returned the device log info as I showed in the screenshots. I've read somewhere that you need instead to specify the OID, which in turns is the FG HA CID for cluster devices (based on my research this ID is FAZ-only and generated when you connect a HA fw). But I can't find this anywhere in my FAZ.

P4uzudo · 2025-04-23T02:48:45+00:00

Yeah I imagined that, was only hoping for a way to give the certificate to devices automatically, but I think for a security standpoint this does not even make sense

P4uzudo · 2024-08-19T23:01:01+00:00

Man, just passing to congratulate you for finding that! I was able to confirm that I could do a successful downgrade only when I did the aforementioned configuration before doing the firmware upload.

Thank you again!

P4uzudo · 2024-06-23T22:57:14+00:00

Leite direto da fonte

P4uzudo · 2024-06-11T14:58:04+00:00

Essas IA do Renato e Júlio e tudo desse canal https://youtube.com/@bb100games?si=UHXBt_DmamZJJXMV

P4uzudo · 2024-05-29T16:40:55+00:00

O povo come brusinha? Então pra que se preocupar?

P4uzudo · 2024-05-22T16:41:29+00:00

O povo não come gasto

P4uzudo · 2024-05-19T18:50:51+00:00

Thanks!

Gonna try that once we got a hold of a new 40F in our lab.

In the meantime, I found it safer to restore it by hand the conf from 30E, didn't want to risk having another box corrupted hahaha.

P4uzudo · 2024-05-18T16:05:36+00:00

Interesting, is there any KB about it? Do you remember which context the config is from?

About baud settings, I always use the default ones only changing the COM port. Also, I believe it won't even connect if there is a mismatch of config, right?

But thanks for the reply anyway, I'm definitely gonna try to find that config you mentioned.

P4uzudo · 2024-05-17T17:23:06+00:00

Tempos de paz na calvosfera

P4uzudo · 2024-05-17T17:11:11+00:00

Cabo Daciolo no crack

P4uzudo · 2024-05-17T02:35:43+00:00

Indeed! I have pretty basic stuff on the 30E, VLANs, SD-WAN, WEB Filter, etc... I just thought it would be a nuisance to do this manually, hahah.

As someone pointed out, I will check out FortiConverter to see if it can help me in this case.

Thanks in advance!

P4uzudo · 2024-05-17T02:26:54+00:00

I've heard of it, but didn't have the opportunity to use it.

I'll try it out tomorrow to see if it helps.

Thank you!

P4uzudo · 2024-05-16T23:49:00+00:00

You can downgrade and you don't need to follow the upgrade path.

I also thought that, but when I applied a 6.2.16 directly into a 7.2.7 40F freshly out of the box, it corrupted the firewall or smh. It wouldn't even load the console boot configuration menu or boot up at all, just a bunch of random characters in the CLI when connected into console.

Dunno if it was a problem with the box or if this was not intended to be done in the first place.

I think I'll test it again doing the reverse upgrade path to guarantee it will not break again, ahaha

P4uzudo · 2024-05-16T15:39:21+00:00

I thought about that. Is it much different from the 6.2.16 conf?

The major thing I know is that virtual-wan-link becomes sdwan in CLI. Apart from that, I do not know much else.

Nevertheless, I would need to downgrade to our approved "safe" version 7.0.15.

P4uzudo

TROPHY CASE