FortiOS 5.2.3 is out

[hklb]

.

[VicAndr · Accepted solution]

...discovered another bug with v.5.2.3. Administrators who are restricted to provision guest accounts only, can't actually print those accounts (to hand over login IDs and passwords to relevant users). In attempt to do so a FortiGate responds with "Error 500: Internal Server Error".

...didn't have this problem before the upgrade [&:].

[Paul_S · Accepted solution]

hklb wrote:

Change your encoding in your browser (in chrome : option - more tools- encoding - western) and it works.

Support said the encoding error will be fixed in 5.2.4

[rwpatterson · Accepted solution]

Also you cannot load the DNS screen.

When upgrading to 5.2.3, the admin accounts have changed from 'super_admin' to 'prof_admin'. We had the same issue here. We simply went into a backup, changed the admin types and restored the config. I did this remotely, hoping I wouldn't have to drive in. It worked flawlessly.

By the way, we got the answer from support. My guru is better than your guru!

[seadave]

Upgraded 100D running 5.2.2 to 5.2.3.  For the most part, running without issue, but I'm getting the following error (see attached JPEG) when I look at address lists:

Invalid octet in UTF-8 sequence when decoding 'string'

Overlong 2 byte UTF-8 sequence detected when decoding 'string'

At the bottom it says:

One or more addresses in this group are associated with an interface (wan1). Only addresses that are not associated with an interface, or are associated with wan1 can be added.

I kind of understand this, but wonder why it didn't show up in 5.2.2?  I tend to use ANY for the interface when I'm creating an IP or FQDN address that I will be using for blocking.  I'm guessing I should be methodically using WAN1 instead?  I wish there was a way to select in the GUI and say change all to WAN1.  I downloaded the config, but when you use ANY, the line:

set associated-interface "X"

is not present for the address definition so I cannot do a simple find/replace.  Ugh.

[dfroe]

dfollis wrote:
Invalid octet in UTF-8 sequence when decoding 'string'

Overlong 2 byte UTF-8 sequence detected when decoding 'string'

There's a very simple solution for this: Clear your browser cache.

[Paul_S]

dfroe wrote:

dfollis wrote:
Invalid octet in UTF-8 sequence when decoding 'string'

Overlong 2 byte UTF-8 sequence detected when decoding 'string'

There's a very simple solution for this: Clear your browser cache.

Clearing my browser cache did not fix this decoding string error. I cleared everything and switched browsers. Still getting error. Opening another ticket. sigh.

[hklb]

Paul S wrote:

dfroe wrote:

dfollis wrote:
Invalid octet in UTF-8 sequence when decoding 'string'

Overlong 2 byte UTF-8 sequence detected when decoding 'string'

There's a very simple solution for this: Clear your browser cache.

Clearing my browser cache did not fix this decoding string error. I cleared everything and switched browsers. Still getting error. Opening another ticket. sigh.

Change your encoding in your browser (in chrome : option - more tools- encoding - western) and it works.

[Paul_S · Accepted solution]

hklb wrote:

Change your encoding in your browser (in chrome : option - more tools- encoding - western) and it works.

Support said the encoding error will be fixed in 5.2.4

[dfroe]

Paul S wrote:

hklb wrote:

 Change your encoding in your browser (in chrome : option - more tools- encoding - western) and it works.

Support said the encoding error will be fixed in 5.2.4

Thanks for sharing this information.

Hopefully we'll have a stable and reliable 5.2 someday before 5.0 is going EoL..

[simonpt]

dfroe wrote:

Hopefully we'll have a stable and reliable 5.2 someday before 5.0 is going EoL..

5.2 updates have been coming out every three months, it appears.  If it's another three months before 5.2.4 comes out, that doesn't give much time before 5.0 goes EOL on 1st Nov. And that's assuming that 5.2.4 is stable and reliable. 5.0 didn't start to get truly stable until update 5 or 6.

[Paul_S]

simonpt wrote:

5.2 updates have been coming out every three months, it appears.  If it's another three months before 5.2.4 comes out, that doesn't give much time before 5.0 goes EOL on 1st Nov. And that's assuming that 5.2.4 is stable and reliable. 5.0 didn't start to get truly stable until update 5 or 6.

well, 5.2.3 came out 3/18/15 so 3 months from that date gives us 6/18/15 which is about 4 weeks from now. That matches the release estimate that I have heard fairly closely.

[Paul_S]

immediately after my last post, I went to reproduce the string decoding error, but it would not happen any more. Not sure why it happened after clearing browser cache, but not now. either it only happens sometimes or it happens once after clearing the cache.

[Paul_S]

now the error is happening again.