Koozali.org formerly Contribs.org

Primay i-bay shows 403

Offline zoran

Primay i-bay shows 403
« on: January 18, 2005, 07:15:45 AM »
OK, I'm at my wit's end...  the error_log shows client denied by server configuration: /home/e-smith/files/ibays/Primary/html  but this was working earlier today, and I didn't mess with the httpd.conf templates.

I've gone through the httpd.conf and can't seem to find where this stuff gets denied...

Can someone please help?

zoran

Offline zoran

Primay i-bay shows 403
« Reply #1 on: January 18, 2005, 07:21:53 AM »
What's weird is that if I use the squid server to connect to the Primary ibay via http, it works fine...  but it logs MY ip address versus the reverse lookup when I try accessing it directly.

All of the i-bys work fine except for the Primary...

Offline zoran

Primay i-bay shows 403
« Reply #2 on: January 18, 2005, 05:41:57 PM »
The only way I got it to work was to change

<Directory />
    Options None
    AllowOverride All
    order deny,allow
    deny from all
    allow from none
</Directory>
 
to

<Directory />
    Options None
    AllowOverride All
    order deny,allow
    deny from all
    allow from all
</Directory>

but I'm not so sure it'a a good dea to leave it like that.  I see that a bit lower in the httpd.conf the primary directory also should be covered:

<Directory /home/e-smith/files/primary/html>
    Options Indexes Includes
    Options +Includes
    AddType application/x-httpd-php .php .php3 .phtml
    AllowOverride All
    order deny,allow
    deny from all
    allow from all
</Directory>

I'm still not sure why this is happening.  Can someone please help?  I can mail you the complete httpd.conf if it would make things easier.

zoran

guest22

Primay i-bay shows 403
« Reply #3 on: January 23, 2005, 10:42:18 AM »
Funny, I have exactly the same....

If I change the 'primary ibays directories' entries  httpd.conf from 'allow from 127.0.0.1 [localip]

to

'allow from all' it works again..

Anybody any idea?

Offline zoran

Primay i-bay shows 403
« Reply #4 on: February 04, 2005, 04:47:34 PM »
RequestedDeletion - have you had any luck?

everytime I create a new ibay, the template gets expanded, and then my primary ibay shows 403 again.

I know I could create a custom template for this, but wy did it all of a sudden stop working is what I'm trying to find out.

Anyone, please can you help?

zoran

guest22

Primay i-bay shows 403
« Reply #5 on: February 04, 2005, 04:57:04 PM »
Hi,

I guess somehow the httpd.conf db values for the primary ibays got 'changed' as if the primary ibay is set to local access only.

Anybody any idea how to reset the db parameters for the primary ibay (public access) back to default pls ?

Offline zoran

Primay i-bay shows 403
« Reply #6 on: February 04, 2005, 04:57:30 PM »
I think this may help, but I'm pretty sure this started happening AFTER I instaled Dan Brown's PHP 4.3.10 rpms.  Does that make sense?

zoran

Henk

Primay i-bay shows 403
« Reply #7 on: February 04, 2005, 05:58:40 PM »
Quote from: "zoran"
I think this may help, but I'm pretty sure this started happening AFTER I instaled Dan Brown's PHP 4.3.10 rpms.  Does that make sense?

zoran


Maybe. I also just saw my primary ibay gives a 404 error. I also installed the same PHP 4.3.10 rpms.

Offline zoran

Primay i-bay shows 403
« Reply #8 on: February 05, 2005, 06:21:02 AM »
By any chance did you install the ftp-manager rpm as well?  I found that I had that set to not allow anonymous access to my primary ibay, but I guess that applies for FTP as well as HTTP.

Is this right?  all of us running web sites on SME are also running anon ftp servers?

guest22

Primay i-bay shows 403
« Reply #9 on: February 06, 2005, 09:40:14 AM »
Hi, just a quick (simple foolish) tip

Check /home/e-smith/accounts

Take a look at the first line with properties for the primary ibay, what is the value for PublicAccess?

For me it changed to 'local' so I changed it back to 'global'. After that a 'console-save' and expand the httpd.conf template and restart httpd. Bingo, back to global access.

Use it at your own risk ;-)