Cant edit some files in www folder using edit file
-
i tried editing using winscp and that too fails
permissions r as below
$ ls -la /usr/local/pkg/miniupnpd.* -rw-r--r-- 1 root wheel 8862 Sep 26 11:37 /usr/local/pkg/miniupnpd.inc -rw-r--r-- 1 root wheel 5051 Sep 26 11:35 /usr/local/pkg/miniupnpd.xml $ ls -la /usr/local/www/system.php -rw-r--r-- 1 root wheel 20278 Sep 21 20:40 /usr/local/www/system.php $ ls -ld /usr/local/www drwxr-xr-x 17 root wheel 8704 Sep 26 11:33 /usr/local/www
-
the CF is almost empty, i just use pfsense and the cron package
-
Almost empty? Pardon me, but if it shows almost empty, there's something very wrong with your FS. That space gives you rougly 450MB per each slice, which is just about enough for basic system. Could you just do a real check what's the space there? Because "almost empty" is nonsense.
$ df -h Filesystem Size Used Avail Capacity Mounted on /dev/ufs/pfsense0 908M 341M 494M 41% /
This is from a 2GB CF nanobsd install. Just 2.2.4 system itself. As you can see there, that's almost 350MB, and the 2.2.5 thing is bigger, due to python being included.
-
$ df -h Filesystem Size Used Avail Capacity Mounted on /dev/ufs/pfsense0 443M 248M 159M 61% / devfs 1.0K 1.0K 0B 100% /dev /dev/ufs/cf 49M 1.1M 44M 2% /cf /dev/md0 38M 572K 35M 2% /tmp /dev/md1 58M 13M 40M 25% /var devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev
-
Well, so much for almost empty. Other than that - backup the config and re-image the card… If that doesn't work, get a new one.
-
seems like other things also broken, i did the below things
- got a brand new 2GB CF card and flashed the last 2.2.5 snap onto it
- booted and came to the web gui
- tried to restore backed up config and the page keeps going on and on
- tried multiple times and even with different browsers but still wont restore the config
now the thing about broken CF card is out of the picture and secondly something as simple as restoring the config using the web GUI should atleast work right, i even tried editing the file also from edit file page and situation is still same
-
Well, install 2.2.2 or older, restore config, upgrade… Again, you are chasing completely fails trails here with 2.2.5. This nanobsd thing got badly screwed with CF cards ever since the filesystem fiddling. Worst being 2.2.3 with the UFS+SU/J nonsense, completely unusable. 2.2.4+ is somehow usable with permanent RW.
Other than that, get a different CF brand. Some of the pfS devs suggested Transcend 133x cards were working well for him.
-
well i keep my CF permanently RW and all the things i tried were with that only but still no luck
to get back online i had to replug old CF.
i dont have much issues in delay while moving from read only to read write, i use SLC cards
-
i mounted CF as RW permanent and then tried using ee to edit the system.php and then it edits fine but when i do it from edit file in gui it doesnt so i guess something wrong in the GUI in some php function or so which could be the cause of config also not restoring
even tried using winscp and am able to edit any file
-
I can't reproduce this here on my ALIX. On the current 2.2.5 snap I can edit /usr/local/www/system.php and the edit works fine.
-
how do we enable debugging in lighthttpd to figure out what is actually happening because no errors appear anywhere so its difficult to figure out whats going wrong
-
Maybe clearing your browser's cache or starting with a new browser on a new PC would help…
-
i tried on chrome, firefox and internet explorer
-
-
from browsers on my PC as well as LAN it doesnt work so i tried even from my mobile and its strange but that works
-
We've been trying to point you to the fact that this ain't a reproducible pfSense issue for anyone but you. Perhaps, reinstall your broken workstation instead.
-
well if the workstation is broken then y does the same browser and same PC edit those files all fine on 2.2.4
-
See suggestion right above. This issue doesn't reproduce anywhere but on your haunted premisses.
-
from browsers on my PC as well as LAN it doesnt work so i tried even from my mobile and its strange but that works
Ok, seems there's an issue with your browsers then. Try clearing all cache, all cookies, disable all plugins/extensions.
-
Ok, seems there's an issue with your browsers then. Try clearing all cache, all cookies, disable all plugins/extensions.
Good advice. Incognito mode tab in Chrome/similar in other browsers that doesn't load any extensions, and doesn't use your cache a good option.