"Could not contact custom update server."

stephenw10

DNS issue would have been my first guess but:

if i SSH into my pfsense box, and ping google.com for example, all is well.

So perhaps not. :-
As a test you could try fetching the package list manually:


[2.0.2-RELEASE][root@pfsense.fire.box]/root(1): fetch -o /dev/null http://www.pfsense.org/packages/pkg_config.8.xml
/dev/null                                     100% of  106 kB  242 kBps

That's under 2.0.2 as you can see. In think 2.1 is using the same package list but I'm not certain of that. Useful test anyway.

Steve

ericab

thanks for all the replies !

@stan,
thats a good idea, but the whole url is there, it just extends beyond the text box

@cmb,
all machines on my LAN and the pfsense box itself can perform name resolution; and i have a default gateway assigned…however, my default gateway is a private address 192.168.1.142; as my pfsense box is behind another router; but 192.168.1.142 is assigned on the DMZ.. not sure if this matters, but could this be a port forwarding issue ?

@stephenw10,
fetching the package list via ssh works as advertised

some other observations:

does this matter?
http://db.tt/UP1OYg85

also,
when i traceroute to pfsense.org... i get this:
http://pastebin.com/rAekJxRG

it goes on and on. is there an upstream problem ?

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.

stephenw10

Yes, pfsense.org does not respond to pings.

Steve

ericab

@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

does anyone have a solution ? ???

stan-qaz

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

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

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

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

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

ericab

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

wallabybob

@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

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

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

problem solved.