lots of bugfixes
https://docs.fortinet.com...release-notes/download
sudo apt-get-rekt
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
You can get a FAZ license for $1 on AWS for 500Gb and up to 2 "home" Fortigate/VDOM (up to Fortigate 90 and VM-01), still have to pay for AWS usage, I'm at around $25 a month.
dfollis wrote:I have a home setup of the following:
FWF-60E v6.0.4 build0231 (6.0.4)
FSW-108D-POE v3.6.9-build0426 (this model does not support v6)
FortiAP FP221C v6.0-build0027 (just upgraded to build0030, 6.0.4)
Fairly simple setup for home using these devices. I've experienced random outages after ~24 hours after upgrading from 6.0.3 to 6.0.4. Symptom is Wifi will be down and hard wire connection to FWF-60E will not respond without a hard power reset.
I first tried to update my FSW from 3.6.8 to .9 but crash occurred again. This AM after another hard reset was needed, I noticed that 6.0.4 for FP221C was released on 1/25 so I have just updated that. As this is a home setup, I'm not paying for FAZ (considering we spend thousands of dollars on FTNT gear at work sure would be nice for free FAZ with low daily limit for home use/testing, just saying :-)).
I do have a synology though so I'm going to enable SYSLOG and dump to that to see if I can get better system events. When I check events logged to FortiCloud I don't see anything odd. Running "diag debug crashlog read" shows the following:
1: 2019-01-26 22:27:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 2: 2019-01-26 22:27:12 <00152> scanunit=manager str="Success loading anti-virus database." 3: 2019-01-26 22:37:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 4: 2019-01-26 22:37:12 <00152> scanunit=manager str="Success loading anti-virus database." 5: 2019-01-26 22:40:14 the killed daemon is /bin/pyfcgid: status=0x0 6: 2019-01-26 22:59:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 7: 2019-01-26 22:59:12 <00152> scanunit=manager str="Success loading anti-virus database."
8: 2019-01-27 12:33:03 <00152> scanunit=manager str="Success loading anti-virus database."
It is interesting that that last event logged is an AV update until I reset it 12 hours later, see events 7 and 8 above.
Not sure if anyone else is seeing stability issues like this. It is possible I have an odd config that is causing an issue as I have a few VLANs that are trunked over my FSW, but nothing unconventional that I'm aware of. Will update post if I see another crash.
Go to support portal.... https://support.fortinet.com/Download/FirmwareImages.aspx
Click on the "Upgrade Path" tab and select your model, current firmware, and Upgrade To FortiOS Version.
Afterwards the page will display the correct upgrade path for you.
I'm going to guess that you can jump from 6.0.2 to 6.0.4. The versions are pretty close.
-DDSkier FCNSA, FCNSP FortiGate 400D, (2) 200D, (12) 100D, (2) 60D
ghorchem wrote:
Captive Portal login with a local username and password on the Fortigate works. With LDAP remote authentication it fails. It did the same thing in 6.0.3 when will this be fixed. We have rolled back to 6.0.2
Hi,
Did you open a support case?
Lucas
New issue:
FortiView > All Sessions (now) : Unable to right click and filter (chrome 71)
Hi,
Mine was returning "admin login failed due to max session" not for invalid password.
Maybe try to remove connection to FAZ in security fabric. Also delete/check status of device in FAZ (I remember having an issue there, device not visible until I reset the FAZ in Security Fabric after upgrading FAZ).
If still don't work, could you post a new threat so we keep this seperate and not polutting this general thread too much?
Thanks,
Stephane
dfollis wrote:I updated my FAZ to 6.0.4 but unfortunately the localhost Admin failed logins are still occurring every 60s. See below, I updated FAZ at 07:38:45, after reboot failed logins started right back up.
itime=1548777151date=2019-01-29time=07:52:30vd=roottype=eventsubtype=systemaction=loginbid=50062dstepid=3dsteuid=0dstip=127.0.0.1dvid=1026epid=3euid=3eventtime=1548777150idseq=205745199928836096level=alertlogdesc="Admin login failed"logid=0100032002logver=60method=httpsmsg="Administrator admin login failed from https(127.0.0.1) because of invalid password"reason=passwd_invalidsn=0srcip=127.0.0.1status=failedui=https(127.0.0.1)user=admin
Final follow up. Happy to report that my FWF60E has been up and running without crash for over 36 hours now. I noticed previously in the FAZ logs that an AV update occurred right before the gate would freeze. I've been using Fortinet products for over 14 years, and I've seen this before. FTNT will push a bad AV/IPS or even AV/IPS engine update and gate will crash. Sometimes this happens for a few days until they figure out the issue and then the problem goes away. Or it could be this, the Admin failed login from localhost (127.0.0.1) was occurring every few minutes. Now it is every 15. I'll open a case regarding that and start a new thread.
VMware fortigate-vm, updated to 6.0.4. Bug in fortiview, table is broken, users login missing. And cant download web filter log from Forward Traffic. Better stay on 5.6...
6.0.4 now installed on 31 firewalls - only issue I had was with the default behavior depreciating TLS 1.0 on SSL offload (full SSL), i.e. I have an old server that only supports TLS 1.0 and I front with the FGT to present TLS 1.2 to the world, but FGT support chat sorted me in a few minutes.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1536 | |
1029 | |
749 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.