Netgate SG-1000 microFirewall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - webmst

Pages: [1]
(for the umpteenth time...)

Almost every time I perform an hw (and pfsense) upgrade, after reloading an old configuration, I consequently realize I cannot access the System-Update-Update_settings tab anymore. If I try, I get a "504 Gateway Time-out error".

I can solve the problem restoring "factory defaults" but when I reload the old configuration, it comes back.

It is obviously a configuration issue but - as setups are very complex to be manually re-entered from scratch - I'm wondering if I can amend the config.xml file.

In trying to figure out what's missing in my old configuration files, I noticed they're always missing the "firmware", "gitsync" and "pkg_repo_conf_path" keys/values in the "system" key from config.xml (all recalled in system_update_settings.php).

As nobody modified config.xml manually before, I suppose these keys got lost during some recent upgrade process, so I think this could be a workaround for many other users upgrading older systems experiencing the same issue.

Can anybody please supply an excerpt of a working config.xml file for the afore said keys in order me to restore proper operation?

Thanks in advance.

Packages / No available packages (empty list)
« on: September 27, 2017, 06:36:16 am »
Hi folks,

I'm still finding the following problem since the change of the system upgrade/package management (last year, now based on the slower "pkg" method).

Again, on a fresh 2.3.4-p1 install (it happens on both a VM full install and an embedded device) I encounter a empty list on "available packages", after having already installed some with no errors.

Has anybody any ideas?
Thanks in advance.

Installation and Upgrades / Unable to update repository
« on: May 08, 2017, 08:39:03 am »
Hi folks,

I'm getting the following symptoms on my NanoBSD-based pfSense box equipped with a 4Gb CF (currently running rel. 2.3.3).

I hasten to add that I had already dealt with the same update problem 2 weeks before and that, to solve it quickly, I had reinstalled pfsense writing the CF from scratch, just to experience it later again. I'm saying this to point out that the problem should be triggered by some background operation, with no specific user action, while the box and all the machines in the network are working perfectly.

So, I'm getting the well know "unable to check update status" message from the GUI dashboard and I can't use the package manager to display installed or to install new packages ("unable to retrieve package info") and I can't even access the "update settings" subpage of the update function from the GUI to select the source ("gateway timeout").

Trying to solve, I checked all the update-related solutions on the forum, with no success (including jimp's solution on sticky posts labelled "2.3.x "Unable to check for updates"/"Unable to retrieve package information").

Infact, trying to execute "pfSense-upgrade -d" or "pkg update; pkg upgrade pkg", I get an "unable to update repository catalogue pfsense-core" warning and the following "unable to update pfsense repository".

Looking at the system logs, I found the following warnings, related to attempted update operations, that seem quite strange and give me no clue:

nginx: 2017/05/07 17:36:44 [error] 48369#100083: *167 upstream timed out (60: Operation timed out) while reading response header from upstream, client:, server: , request: "POST /pkg_mgr_installed.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "", referrer: ""

nginx: 2017/05/07 17:43:33 [error] 48771#100098: *213 upstream timed out (60: Operation timed out) while reading response header from upstream, client:, server: , request: "GET /system_update_settings.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "", referrer: ""

Has anybody any ideas except reinstalling the system once again?

CARP/VIPs / CARP scripts surviving an upgrade / enhancement proposal
« on: July 26, 2015, 04:39:04 am »
Hi folks,
I was wondering if there is an "official way" to preserve some lines of code added at the end of the CARP scripts (rc.carpmaster/rc.carpbackup).

I've noticed that those files are always rewritten during an ugrade, leading to a loss a functionality that has to be restored manually later.

Anyway, I suppose that a definitive solution would be to implement a simple GUI "CARP actions customization page" of user-specific code (to be called after system actions in the above said files), i.e the selection of a custom script file (stored in the pfsense configuration file), so that all customizations can survive an upgrade. This would be very useful, as it is becoming common to provide spinoff actions for a CARP status change.

Pages: [1]