Jump to content

  • You cannot start a new topic
  • You cannot reply to this topic

403 Error - Payment Plugin Rate Topic   - - - - -

 
  • MarkusBudz
  • Member
  • Trial users
  • Join Date: 08-Aug 18
  • 23 posts

Posted 18 February 2019 - 10:51 AM #1

Hello,

 

right now i get a payment plugin programmed for my site. The bank server has to ask if the connection is still there before the payment gets authorized. For this a conformation script has to be called. The problem is that i get a 403 forbidden error when i want to call the script. I set up the file rights correctly and already asked my host if there are some specific security settings that should be modified on the webserver. But they also couldn´t find the problem why i get a 403.

Then I also tried this:  http://kb.cs-cart.co...ceptable-errors

Still no solution.

Anybody knows how the problem could be solved?



 
  • galtinbaeva
  • CS-Cart Expert
  • Authorized Reseller
  • Join Date: 06-Dec 13
  • 3303 posts

Posted 26 February 2019 - 05:58 AM #2

Hello,

 

right now i get a payment plugin programmed for my site. The bank server has to ask if the connection is still there before the payment gets authorized. For this a conformation script has to be called. The problem is that i get a 403 forbidden error when i want to call the script. I set up the file rights correctly and already asked my host if there are some specific security settings that should be modified on the webserver. But they also couldn´t find the problem why i get a 403.

Then I also tried this:  http://kb.cs-cart.co...ceptable-errors

Still no solution.

Anybody knows how the problem could be solved?

 

Hello,

 

Where is your confirmation script located?


Simtech Development | sales@simtechdev.com | www.simtechdev.com
CERTIFIED CS-CART PARTNER | LICENSES | DEVELOPMENT | ADD-ONS | DESIGN | UPGRADE

Google Analytics Enhanced Ecommerce - get advanced ecommerce analytics


 
  • MarkusBudz
  • Member
  • Trial users
  • Join Date: 08-Aug 18
  • 23 posts

Posted 06 March 2019 - 01:59 PM #3

The problem is already solved. Like you have assumed the script was in the wrong location.