Hello Alan,

Torsten Lehmann wrote:

...

http://wiki.freeradius.org/ (or faq) returns: Forbidden

* Alan DeKok <aland@deployingradius.com> [2012-05-09 09:44]:

It works for me. We upgraded the machine, and had a few problems with editing the wiki. But it should be OK now.

for me it does not, I still have the problem. If you want I can record the problem for you as flash video. I'm using github to authenticate. Cheers, Thomas

On Wed, May 9, 2012 at 2:51 PM, Thomas Glanzmann <thomas@glanzmann.de> wrote:

Hello Alan,

...

Torsten Lehmann wrote:

...

http://wiki.freeradius.org/ (or faq)  returns: Forbidden

* Alan DeKok <aland@deployingradius.com> [2012-05-09 09:44]:

...

It works for me.  We upgraded the machine, and had a few problems with editing the wiki.  But it should be OK now.

for me it does not, I still have the problem. If you want I can record the problem for you as flash video. I'm using github to authenticate.

It works for me, with ot without github auth. I suggest you try different connections (e.g. just in case your ISP block the traffic somehow) and different station (e.g. just in case your browser cache the response). -- Fajar

Hello everyone, * Thomas Glanzmann <thomas@glanzmann.de> [2012-05-09 09:58]:

for me it does not, I still have the problem. If you want I can record the problem for you as flash video. I'm using github to authenticate.

I have problem editing the page, accessing is fine. But Arran seems to fix that. Cheers, Thomas

Hello Alan,

...

Torsten Lehmann wrote:

...

http://wiki.freeradius.org/ (or faq) returns: Forbidden

* Alan DeKok <aland@deployingradius.com> [2012-05-09 09:44]:

...

It works for me. We upgraded the machine, and had a few problems with editing the wiki. But it should be OK now.

for me it does not, I still have the problem. If you want I can record the problem for you as flash video. I'm using github to authenticate.

Cheers, Thomas

I hate to jump on the "me too" bandwagon, but it is still also down for me, with a 403 Forbidden code. Steve

And it's back... Turned out to be some CSRF protection that got added in a later version of rack-protection (a package for preventing CSRF attacks for rack). Anyway it was getting tripped by nginx rewriting the host header in requests to be itself, instead of the original host, and hence the random 403 forbidden message. Of course they didn't provide any log messages to explain why rack protection was returning a 403 error, which is why it took a day to go through the code and find out exactly what was happening. Anyway, all synced up with Gollum 2.0 now and using all the latest gems. Seems like a few CSS bugs have been fixed with rendering code blocks, and few added which have caused the font sizes to go a bit wonky in pages... Should get to most of them over the new few days. Looks like they *finally* fixed the duplicate title issue too. Oh and there's now a 'Sponsored by' link at the bottom of the page, as they're the company who's actually paying for the hosting ;) Apologies for the down time/ Arran Cudbard-Bell a.cudbardb@freeradius.org Betelwiki, Betelwiki, Betelwiki.... http://wiki.freeradius.org/ !