Getting 403 connecting to Custom Store on Laravel Forge

[Lab385]

• I've tried my luck with Shipstation support but they're insisting I'm doing it wrong.
• Clicking the Test Connection button works, but 'Connect' returns 'Request failed with status code 403'
• A curl with basic auth works fine.
• Ive set up Shipping statuses and Matrix field.

As Laravel Forge runs Nginx I wonder if it's not passing the auth, so tried adding this to location in nginx conf but to no effect:

proxy_set_header Authorization $http_authorization;
proxy_pass_header  Authorization;

[johnnynotsolucky]

@Lab385 could you provide some more information so we can investigate the issue more thoroughly:

• Version of Craft
• Version of Craft Commerce
• Version of this plugin

Could you also confirm

• that the URL you've captured in "URL to Custom XML Page" on the ShipStation custom store form matches the URL provided by the plugin in the plugins settings page
• and, that you can make a request to the export endpoint

The plugin doesn't output an HTTP 403. If the username/password combination is incorrect you should see an HTTP 401 response instead.

A request such as the following can be used to test whether exports work correctly:

curl --location 'https://<your host>/actions/shipstationconnect/orders/process?action=export' \
  --header 'Authorization: Basic <username:password>'

The authorization header value is a base64 encoded string of username:password.

[Lab385]

Hi @johnnynotsolucky Craft Pro 4.5.9 Craft Commerce 4.3.1 ShipStation Connect 2.0.3 Yes, I’ve copied the link straight out of the Shipstation Connect plugin and the curl returns a list of orders.

…

On 25 Oct 2023 at 4:42:11 pm, Tyrone Tudehope ***@***.***> wrote: @Lab385 <https://github.com/Lab385> could you provide some more information so we can investigate the issue more thoroughly: - Version of Craft - Version of Craft Commerce - Version of this plugin Could you also confirm - that the URL you've captured in "URL to Custom XML Page" on the ShipStation custom store form matches the URL provided by the plugin in the plugins settings page - and, that you can make a request to the export endpoint The plugin doesn't output an HTTP 403. If the username/password combination is incorrect you should see an HTTP 401 response instead. A request such as the following can be used to test whether exports work correctly: curl --location 'https://<your host>/actions/shipstationconnect/orders/process?action=export' \ --header 'Authorization: Basic <username:password>' The authorization header value is a base64 encoded string of username:password. — Reply to this email directly, view it on GitHub <#57 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDPVUXDRGJPUWOZBKT56HHTYBDGGHAVCNFSM6AAAAAA6NK6BXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZYG44TCNBRGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[johnnynotsolucky]

@Lab385 it seems like the problem lies somewhere between your site and ShipStation. You'll need to figure out where the fault is.

As a first step, you can confirm that ShipStations requests are indeed reaching your server:

In Laravel Forge, you can view nginx logs by

• Navigating the relevant server,
• Selecting "Logs"
• Then from the "View Log" drop down, choosing either Nginx Error or Nginx Access logs.

Attempt to create the connection in ShipStation, refresh the access log and verify that a new access log appears. If it errored, you should still see the log, but with an error HTTP code. Then you can have a look at the error log for potential causes.

I'm going to close this for now because it looks like it's not a problem caused by the plugin directly.

However, please reach out to me on the Craft Discord, I have the same handle as on Github, and I can assist further.

[terryupton]

Did you manage to resolve this @Lab385 as I am seeing the same issue.

[Lab385]

Did you manage to resolve this @Lab385 as I am seeing the same issue.

@terryupton it was an issue with the actual Shipstation account, from what we could see. I created a new test account, the integration worked fine, so we moved everything across.

[johnnynotsolucky]

@terryupton what specific issue are you seeing?

The steps in the comment above should help you diagnose where the problem lies.

[terryupton]

Hey @johnnynotsolucky and @Lab385 - thanks for the replies.
I managed to resolve this by adding the .htaccess file with the following:

CGIPassAuth On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]