-
-
Notifications
You must be signed in to change notification settings - Fork 374
404s on the Proxy URL #45
Comments
Is your proxy route Your route It would then look something like this: Route::any('/proxy', 'ProxyController@index')->middleware('auth.proxy'); Then within the Shopify partners panel you could set your proxy url to: |
Hi @ncpope , thanks for your input! I do have the sample home route that came with the default install: Route::get('/', 'DashboardController@index')->middleware('auth.shop')->name('home'); I then have created a minimal test case for the Route::get('/proxy', function () {
return response('Hello, world!', 200)->withHeaders(['Content-Type' => 'application/liquid']);
})->middleware('auth.proxy'); On the app proxy settings in Shopify, I have it setup pointing to the root URL: And was trying to hit the proxy URL by visiting the namespaced url at: https://3c887b11.ngrok.io/apps/product-builder as this was the app proxy URL on the test site: I think I'm missing something, but can't quite understand what. I was expecting that by hitting the store URL above, I would get the Thanks so much for any insights on this you may provide. |
Hi @lmartins This is what is happening when you have a proxy and Shopify handles a request to that proxy url:
This is how you would fix your issue: Inside of your shopify partner panel you need to set the url to The /apps/product-builder is for the shopify store, the url you enter below that is the url that Shopify will call when a user visits that shopify url. |
ahhh that did the trick!! |
Sorry for all the questions.
I'm still a bit puzzled with the site communication with the app via proxy.
I have the app proxy setup as follows:
When i visit the store URL that is linked to this proxy, I see the activity showing up in the ngrok log, however it seems to return an HTML with a redirect in it:
On the frontend the network activity shows the following:
Any idea what would cause this?
Thanks so much for any help you may provide.
The text was updated successfully, but these errors were encountered: