404 NOT FOUND!!!

Hugel

after i clear the cache of pfsense. The webgui show 404 not found but after that i try to connect in internet (ok). Please help me to solve this problem. My Boss got mad at me.

PFSENSE Ver. 2.1.5 bsdfree.

can i upgrade my pfsense version to the latest to improve my internet connection.

DOES ANYONE CAN HELP ME.

doktornotor

Perhaps someone can help you after you have installed a supported pfSense version.

https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD

stephenw10

Indeed, you should run something more current preferably actually the current release.

However upgrading is more difficult when you can't access the upgrade button!

What exactly did you clear?

What page exactly are you now trying to access that is reporting 404?

Do you have ssh/console access?

Steve

kuyaMacoy

Same problem, after i clear my squid cache. (var/squid/cache)
Then 404 not found appear. Please help

stephenw10

Same pfSense version?

Every page in the gui?

Steve

kuyaMacoy

Yes sir, when i try to access my web gui (192.168.200.30) it says 404 nit found, but i have internet. Pls help

jahonix

Reboot via console (telnet/ssh or serial)

stephenw10

Every page is showing 404?

That seems unlikely to be a missing page then. Clearing the squidcache is the only thing you did?

Do you have ssh or console access? If so reboot from there as suggested.

Steve

xalex1977

Hi,
I have the same problem, pfsense version 2.1.4,
webgui error 404 - not found

I deleted the cache with the command:
cd /var/squid/cache, rm -rf *??

help !!!

Gertjan

@xalex1977 said in 404 NOT FOUND!!!:

help !!!

The one and only guy that still uses pfSense 2.1.4 today, that must be you. So you're the expert.
(no expert ? then upgrade to the actual version 2.4.4-p2 as of today, or at least 2.3.5 if you you are 4x8 bit bound - your problem will be solved, as are dozens of security issues. Big bonus : forum help will be useful again for you)

Some general help, valid for any web server/browser errors :
Check the web server log for any 'request' errors.
I don't want to be the silly guy, but if you use an old version, did you kept the documentation of the old version ?
If not : see here how to check logs on pfSense manually https://docs.netgate.com/pfsense/en/latest/monitoring/working-with-binary-circular-logs-clog.html using the console access.
Hit the F12 key on your keyboard and check what file your browser is loading.

xalex1977

@xalex1977 said in 404 NOT FOUND!!!:

cd /var/squid/cache, rm -rf *

I solved !!!
with the help of the forum user I checked in: /usr/local/www and it was empty, I copied the files from a full backup and now it works

I had run the command: cd/var/squid/cache, rm -rf *
from webgui "Execute Shell command" and has deleted /usr/local/www not /var/squid/cache

xalex1977

@gertjan

I can not update the version because it is modified with samba 3 and active directory authentication;
we have the login with the space between name and surname and samba 4 it does not seem to support
Thanks

Grimson

@xalex1977 said in 404 NOT FOUND!!!:

I can not update the version because it is modified with samba 3 and active directory authentication;

Then you are a certified moron and should not be in charge of a firewall. Running such an old build with countless security issues is borderline criminal and should be a reason to get fired.

Gertjan

@xalex1977 said in 404 NOT FOUND!!!:

from webgui "Execute Shell command"

Dangerous commands, like

rm -rf ....

should not be executed from the from webgui "Execute Shell command".
Never.
Period.

What happened is this :
You executed

cd/var/squid/cache

I presume you know what this does.

But when the GUI get back the result of that command - it shows nothing, the 'command' sessions (a shell command session) it is closed, and it environnement is destroyed.

Then you launch your rm -rf .. command.
This command will be executed on the 'place' where the web-shell is launched. As you have found out yourself : /usr/local/www/ the GUI web root.

You should have done this :

rm -rf /var/squid/cache/*

But, again, don't. Use the console access for this. It's far more saver.

chrismacmahon

I'm going to lock this thread.

Yes you need to update, the sooner the better; your perimeter defense is old, insecure, and out of date.