CSRF verification failed. Request aborted.

[tsm3112]

I have installed FreeNAS last week,worked GUI and SSH well. But i am not able access GUI from yesterday morning, tried in different browsers, enabled cookies, cleared history & cache but no luck, Please help.

 

[dlavigne]

Does deleting the browser cache, history, and cookies fix it? Or using another browser? Or enabling cookies (if they are disabled)?

 

[tsm3112]

I don't think so, I am new to FreeNAS, followed some threads from internet. Thanks.

 

[dlavigne]

I don't think so, I am new to freenas, followed some threads from internet. Thanks.

Does that mean you tried all 3 of those suggested solutions and the problem persists?

 

[tsm3112]

Does that mean you tried all 3 of those suggested solutions and the problem persists?

Yeah.

 

[dlavigne]

It's not a GUI issue, it's a browser issue. If the suggested solutions don't fix it, you'll need to research how to fix CSRF errors for your particular browser.

 

[tsm3112]

It's not a GUI issue, it's a browser issue. If the suggested solutions don't fix it, you'll need to research how to fix CSRF errors for your particular browser.

Okay Thanks

 

[tsm3112]

Hi, I am new to freenas, I am able to ssh to server but suddenly unable to login web UI, Pls help.

 

[ethereal]

which version of freenas are you using ?

have you tried a different browser ?

did you follow the advice of the error message ?

 

[SweetAndLow]

Read the rules and provide some information that people can use to help you.

Freenas version, hardware specs, error messages, screenshots should all be part of your post.

Sent from my XT1096 using Tapatalk

 

[Stux]

Try purging your browser cache.

 

[tsm3112]

I am using freenas 11, tried in different browsers like chrome, firefox, IE, safari, and opera.
Yeah i followed error message advice.
My server details:
HP Proliant SE326M1R2
CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz (2666.81-MHz K8-class CPU)
root@freenas:/ # dmesg | grep memory
real memory = 69122125824 (65919 MB)
avail memory = 66744786944 (63652 MB)

 

[ethereal]

Try purging your browser cache.

 

[Redcoat]

Hello again. This is your 4th thread opening on the same topic. On each one you got some advice. It would assist everyone trying to help you to be able to see all the previous advice and your responses to it - so please add on to a thread, not open a new one, when it's the same topic.

Now to this problem - this is a browser issue, not a FreeNAS issue. For some reason either cookies are not being enabled or your browser cache is not being cleared.

This is what I would do after reading your several threads and responses. Maybe others will have alternative ideas...

Uninstall all the browsers from the Control Panel, Programs and Features page (of course except whatever is native to the version of Windows you are using, so except IE and perhaps Edge, which are not available for deletion). Reboot, open browser, clear temporary files, history, cookies, web forms, everything. Reboot, open browser, clear everything again.

Clean install Firefox (refuse any prompts to import anything if there are such), open Settings, Privacy and ensure that the history is clear - if not, clear everything from it, and try accessing the GUI.

Let us know what happens.

 

[Ericloewe]

I merged another identical thread I found.

 

[Stux]

In my case, I think this issue was triggered when I re-used an IP for FreeNAS which was previously used for a different web-based thing. Say pfSense.

 

[tsm3112]

First i would like to say my sincere apologies for creating multiple threads on the same issue, I am new to the forms and didn't do it willingly.

I have tried with all solutions provided in the earlier suggestion, tried with different browsers and on different machines.

Information about my server:

HP Proliant SE326M1R2
CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz (2666.81-MHz K8-class CPU)
avail memory = 66744786944 (63652 MB)


Storage:
2*480GB intel SSD in RAID 1 (OS Drives)

5*1.9TB Seagate SAS in RAID 5
1*1.9TB Seagate SAS in RAID 5 Spare.

With above 5 drives made a volume and using as a ESXi datastore


Firewall:
Fortinet 100D firewall 1
Fortinet 100D firewall 2

I am ale to ssh to the server and volume is live and accessible through ESXi.

Thanks

 

[Redcoat]

Well, I don't feel I have enough experience with EXSi and its potential influence(s) on FreeNAS behavior to carry this discussion so I will be deferring to others that do.
But I do anyway have some questions to better my understanding:
Was/is your CSRF problem experienced with the setup you have just described?
Given the above screen capture, does this mean that you now have a new problem - your correct root password not being accepted?
Do you have drives passed through for FreeNAS?
Is your Firewall influencing your browser communication with FreeNAS?
I will be following with interest.

 

[tsm3112]

Well, I don't feel I have enough experience with EXSi and its potential influence(s) on FreeNAS behavior to carry this discussion so I will be deferring to others that do.
But I do anyway have some questions to better my understanding:
Was/is your CSRF problem experienced with the setup you have just described?
Given the above screen capture, does this mean that you now have a new problem - your correct root password not being accepted?
Do you have drives passed through for FreeNAS?
Is your Firewall influencing your browser communication with FreeNAS?
I will be following with interest.

Thanks for your reply, When i use IE i am getting below error, It is even not showing login screen,


When i use Other browsers like Chrome, Firefox it is showing login screen but not accepting any username and password which i have used earlier.



I have this issue on the above given server only.
I don't think firewall is stopping this because it worked good first one week, After that we didn't change any thing in firewall.
Thanks.

 

[Maxime Morin]

I have the same error with the old login. I can't login via HTTP, nor HTTPS (connection refused). For the HTTP error, the set cookie directive is sent with the secure flag.

Set-Cookie: csrftoken=1Gl...0ten; expires=Sat, 06-Oct-2018 03:37:49 GMT; Max-Age=31449600; Path=/; Secure

The login request is made over HTTP, so it won't send the cookie, hence the error.

On a side note, I was able to log on HTTP with the demo UI...