2 Issues

Status
Not open for further replies.

Chadi

Explorer
Joined
Aug 24, 2012
Messages
74
Set up hostname as nas.mydommain.com in NAS config and on my domain's DNS zone to point to the NAS IP address.

Problem is, when I access nas.mydomain.com I get this 403 error:

Code:
Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.


Another error I noticed, not sure what this means about "channel 2 memory error"

Code:
[root@nas] /var/log# tail -f messages
May  6 11:33:11 nas MCA: Vendor "GenuineIntel", ID 0x206d7, APIC ID 37
May  6 11:33:11 nas MCA: CPU 17 COR (1) MS channel 2 memory error
May  6 11:33:11 nas MCA: Address 0x6e55ed440
May  6 11:33:11 nas MCA: Misc 0x122940040004208c
May  6 11:33:11 nas MCA: Bank 10, Status 0x8c000050000800c2
May  6 11:33:11 nas MCA: Global Cap 0x0000000001000c12, Status 0x0000000000000000
May  6 11:33:11 nas MCA: Vendor "GenuineIntel", ID 0x206d7, APIC ID 32
May  6 11:33:11 nas MCA: CPU 12 COR (1) MS channel 2 memory error
May  6 11:33:11 nas MCA: Address 0x6e55ed440
May  6 11:33:11 nas MCA: Misc 0x122940040004208c


I'm running 9.10 stable.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Do you have your FreeNAS GUI exposed to the internet. That's a bad idea if you do.
 

Chadi

Explorer
Joined
Aug 24, 2012
Messages
74
I'm sorry but what do you mean by that? What's the purpose of them creating the GUI if it shouldn't be accessible? It's only accessible to me, no one else anyway.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Accessing from your LAN or accessing externally from the internet?
 

Chadi

Explorer
Joined
Aug 24, 2012
Messages
74
Externally, but only I know the web address & IP. It's private info.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Well FreeNAS was not designed or intended to be internet facing, it's intended to be an appliance used on a local network.

I would strongly suggest that you read the post linked here and follow these instructions if you intend to continue to access the GUI via the internet.

Edit: It seems you didn't learn from your earlier experience so I will leave you to figure this out on your own. Good luck.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Externally, but only I know the web address & IP. It's private info.
...except to any portscanning script kiddie who scans your IP block. Nothing on FreeNAS can be safely exposed to the Internet, with the possible exception of ssh (if properly configured). But, as @Jailer notes, it looks like you've been down this road before, and haven't learned much (if anything) from it. Here's the really simple take-away: If you want to access your FreeNAS box remotely, set up a VPN.

As to your other question, it means you have a memory error, just like it says. One of your DIMMs is bad, or the socket is bad, or perhaps your CPU socket is bad.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
I would strongly suggest that you read the post linked here and follow these instructions if you intend to continue to access the GUI via the internet.
Not a big fan of that one, as it relies on SSH port forwarding, which I don't think is nearly as clean a solution as a VPN--though it's still secure. But I guess there isn't an equally-good write-up on a VPN setup.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
I don't think is nearly as clean a solution as a VPN--though it's still secure.
Agreed, but it was the only forum how to that I know of to point him towards before his setup self destructs.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Yeah, we probably need something on how to set up a VPN, except that a VPN is ideally done on the edge device (i.e., the router), and thus doesn't have much to do with FreeNAS at all. It's trivial with pfSense, of course, and some of the better consumer-grade routers have VPN support as well. Though this thread might do the business.
 
Status
Not open for further replies.
Top