By Chris Chase on Saturday, 29 March 2014
Posted in Technical Issues
Replies 6
Likes 0
Views 832
Votes 0
Hello there,

I am receiving a 403 access forbidden error when sending the LinkedIn request back to one of our websites.

I've provided information below.

Thanks
Hello Chris,

Just to confirm with you, your issue has solved already? Please advise.
·
Tuesday, 01 April 2014 10:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Chris Chase,

I am really sorry for the delay of this reply as it is a weekend for us here.
I have tried to click "Sign in with Linkedin" from Linkedin autoposting configuration page, then hitting this :

403 Forbidden

You don't have permission to access /administrator/index.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Hmm, could you mind consult this with your Webhosting provider and see if could help? It seems like when you click "Access" when pop-up the LInkedin account authorization, then it can't redirect back to the configuration page, the token access also can't able to store in database, so it failed.
Keep us updated if Webhosting provider say not related this permission issues.
·
Saturday, 29 March 2014 09:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Arlex,

We actually host the websites ourselves on a shared environment However, when checking permissions everything checks out just fine. All directories within Joomla (apart from a few) are set to 755 and files are set to 644 (apart from configuration.php).

The database user has all permissions needed to write into the database, and disk space is completely fine. In the raw access logs on this account, it shows the return stage of the API call came back with a 404 as from the request. I am unsure why this would be, but I also checked the LinkedIn application and everything is set to their new standards (including rw_nus and rw_company_admin being checked).

We did previously have this site moved to a new hosting account, and we may have a module issue on Apache causing the issue.

Let me reach out to them, but in the meantime is there any insight you can provide?

Thanks,
Justin
·
Tuesday, 01 April 2014 09:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Just an update, this was caused by a rule in Apache.

Thanks for your assistance,
Justin
·
Tuesday, 01 April 2014 09:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nik,

Yes it has. Thank you!
·
Tuesday, 01 April 2014 10:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

You're welcome.
·
Tuesday, 01 April 2014 10:40
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post