"Could not contact custom update server."

stan-qaz · Mar 28, 2013, 6:00 PM

You have the exact DNS setup I show on my status page.

My traceroute from here ends at the same spot yours does, likely that they disabled the responses traceroute needs beyond the last one that responded.

I have no clue why it isn't happening, if I get time today I'll try changing my updater to the snapshots and see if it picks up a new one, been doing it manually up to now.

stephenw10 · Mar 28, 2013, 8:06 PM

Yes, pfsense.org does not respond to pings.

Steve

ericab · Mar 28, 2013, 10:57 PM

@stan-qaz:

You have the exact DNS setup I show on my status page.

My traceroute from here ends at the same spot yours does, likely that they disabled the responses traceroute needs beyond the last one that responded.

I have no clue why it isn't happening, if I get time today I'll try changing my updater to the snapshots and see if it picks up a new one, been doing it manually up to now.

ok thanks,
i wouldnt mind doing it manually myself,
but its not being able to update/install packages that's really something i cant live with.

ericab · Mar 29, 2013, 7:37 PM

does anyone have a solution ? ???

stan-qaz · Mar 29, 2013, 11:21 PM

I gave the auto-update from the snapshot server a try and got the same response you did.

Looking at what is going on I believe I see the problem's cause. The update and snapshot servers store the files in a very different format, the updater apparently doesn't see the snapshot server as a valid update source.

Updates: http://updates.pfsense.org/_updaters/amd64

Snapshots: http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_RELENG_2_0/updates

Manual method is working just fine for me, the shell's manual update will likely work too.

ericab · Mar 30, 2013, 2:26 AM

thanks for the reply stan;
im not 100% sure what the end result should be on the servers custom updater url should be, but int he end i dont think this is the fix for this, as addon packages are not gotten from the mentioned url's.

there is for sure something else going on here.

ericab · Apr 2, 2013, 1:52 AM

any help ? ???

i can see in the logs:

php: /pkg_mgr.php: XMLRPC request failed with error 5: Didn't receive 200 OK from remote server. (HTTP/1.0 303 See Other)

cmb · Apr 2, 2013, 5:39 AM

Run:
fetch http://www.pfsense.org/packages/pkg_config.8.xml

then:

cat pkg_config.8.xml

what's in that file? Should show more about what that 303 is. You're not getting a 303 from us.

ericab · Apr 2, 2013, 10:26 AM

well, the file contains what its supposed to… so this isnt an IP issue... hmm

ericab · Apr 3, 2013, 2:27 AM

so if this isnt an IP issue, where in the filesystem can i look to remedy this ? ???

wallabybob · Apr 3, 2013, 7:20 AM

@ericab:

so if this isnt an IP issue, where in the filesystem can i look to remedy this ? ???

As of a few hours ago the dropbox postings associated with this topic had all disappeared. That makes it hard for anyone who longer remembers the details to find them. (I think it is better practice to post text associated with the topic in a reply, possibly quoted or in tt (TeleType) style and to post graphics such as screen shots as attachments.)

Since fetch allegedly gets the file correctly but the package menu apparently doesn't PERHAPS one or more files were corrupted on your recent install.

PERHAPS your file system is nearly full. What is the output of pfSense shell command```
df


PERHAPS your hard drive is failing (developing bad blocks).

cmb · Apr 3, 2013, 8:03 AM

Browse to pkg_mgr_settings.php (no link, type in manually), are you pointing to the real package server there or somewhere else? Some outside sites give instructions to run a script that changes your system's packages source to some other server we have nothing to do with. Given the 302 and the fact you can manually fetch the package list, that seems likely.

ericab · Apr 5, 2013, 7:10 AM

well nothing worked;
i decided id wasted enough time, reinstalled and built up from scratch.

problem solved.