Pf 2.5.1 fresh install 6try and 6 big 404 not found
-
I did try pf2.5.1 dvd iso install today, as i did lot of fresh install to try out last week with 2.4.5 and 2.5 So nothing have change in my process, no setting different, exactly the same process. But with the new 2.5.1 : we got an happy : 404 Not Found nginx as result . When you try to load up the console web page. Yes it can be ping and wan internet do work on the lan, but you cannot access the console web gui. I log over the wan and try to put the webconfigurator in http and this one just give time out on lan and you can't log anymore from wan due to authetification error.
Right at the first boot: it's possible to do the welcome config, but as soon you hit apply/reload. a big 404 not found came after. yes, same after reset. i can do pass the nag screen at first login when logged from the wan.
So how does a simple usual install turn into a not working anymore with version 2.5.1. ?installing is still about 4 entr, your write the vmx , remove those bogon stuff, set the hostname , ip, password. then it should be it. but not. Mikrotik on that are quite good on their firmware naming and those can equal as being : Pf 2.4.4 being long term version / 2.4.5 : stable version / current test version: 2.5 / Developpment Beta ; 2.5.1
-
even doing a std install and then changing the ip after result into a big 404.
78421#100118: *34 "/usr/local/www/cgi-bin/luci/index.php" is not found (2: No such file or directory), client: 192.168.70.8, server: , request: "GET /cgi-bin/luci/ HTTP/2.0", host: "192.168.70.1"
-
the whole / cgi-bin folder is missing as soon you change ip. haven't try to put an old backup. And after reboot and doing restart webconfigur.. do nothing as the folder being missing.
-
Not sure what your trying to access, but pfsense doesn't use luci - that is a openwrt thing is not. And there is no cgi-bin directory..
-
humm thank i did a speed test bethween owrt and pf and somehome the cache of the browser kick in.. putting straight :https://192.168.70.1/status_logs.php did resolve finally. haaa such a waste. But on fresh it did give a 404. anyway i somehow get 1 working one of 7.
-
Well yeah when you try to access something that is not there, then yeah you get a 404 ;)
-
Browsers 'helping' the users....so aren't helping.
-
I think someone already reported about this problem with v. 2.5.1.
-
Reported what? That the users browser was trying to load a url from openwrt? How is that have anything to do with pfsense?
-
@johnpoz calmati per favore. I think what he is trying to tell, his previous pfsense worked, why is the current version 2.5.1 not.
I really do understand his and many users frustration about pfsense version 2.5 above. -
@akegec Well indeed i do waste lot of time to install and re-install. This is the first time i did see that error and i did lot of fresh install lately. yes i put the wrong error log, but the nginx was straight after you push enter at the login screen. So let say the solution is to not change the subnet and don\t write a domain name at install. do some config (i just install vpn client, alias, set nat and set rule. and then after backup. change the sub
-
What this user was running into had zero to do with 2.5.1, 2.5.0, 2.3.2 version of pfsense.. This is full blown PEBKAC.. user error... Trying to hit his pfsense IP with some url that doesn't freaking exist.. So yeah its going to give you a 404..
How may times the user OP tried to reinstall or install or clean install had zero to do with anything.. Zero..
Have users reported issues - sure, this had zero to do with any of them or pfsense no matter what version.. Pure and simple PEBKAC..
Users frustration - quite often is self inflicted as well ;) And then they try and blame it on whatever upgrade.. Not saying there is not issues with 2.5.0 or 2.5.1, etc. But every little thing that happens is not always related to your firewall and an upgrade.. For example this is a perfect example of pure 100% adulterated user error, and thinking it had something to do with pfsense..
Other than not able to clean install zfs on 21.02 - I have had zero issues with it or p1 or .2.. That was reported, they fixed it - and with .2 I migrated to zfs via clean install.
-
@johnpoz said in Pf 2.5.1 fresh install 6try and 6 big 404 not found:
Users frustration - quite often is self inflicted as well ;) And then they try and blame it on whatever upgrade.. Not saying there is not issues with 2.5.0 or 2.5.1, etc. But every little thing that happens is not always related to your firewall and an upgrade.. For example this is a perfect example of pure 100% adulterated user error, and thinking it had something to do with pfsense..
I might be wrong but I think it is not wise to say things like that, while a lot pfsense users already reported bugs on version 2.5 and above.
One thing my grandpa Stevan always told me,
"If you can't be a good person, at lease be a fair person." -
@akegec you need to back up friend. Read and understand the above. Stay on topic...the topic is very clearly not a pfsense issue.
The browser was 'helping' by adding unnecessary folder and url information for a completely separate product based on a recycled IP address.
User did not notice....did not look at install docs to note proper URL....then tried to blame product.This is like driving around at night with the headlights off because the headlights knob is in a different place between a ford and a mercedes.... don't blame the car.
-
@skogs OP already found the solution on his own. I was talking about johnpoz's statement. Even some hardcore pfsense fans admitted about pfsense 2.5 and above versions problems.
-
Yes, whatever problems there may be in 2.5.X, this is not one of them.
Locking this.
Steve
