You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for making powprox, it's made development easier for me. Unfortunately I'm currently running into some issues which I've traced down to powprox. I'm running osx 10.11.4.
Accessing the .dev domain with http it works, but with https some of the "later" resources (such as @imports in css files & images) fail with a 503 result. The images & css files aren't big (< 1MB), and there are only about 20 total requests, of which ~6 fail.
I've updated the nginx config to write an error log, in which the following message matches requests returning 503: an upstream response is buffered to a temporary file /usr/local/var/run/nginx/proxy_temp/1/16/0000000161 while reading upstream. I tried applying various fixes I found online to no avail.
The requests in question - I'm looking in the browser's network inspector - have the same request headers, but fewer response headers, specifically: status: 503, server: nginx/1.10.2, date, content-type, and x-pow-template:application_not_found. My guess is that the proxy configuration isn't setup to handle file buffered responses, but I'm not sure how to verify or resolve it.
I installed powprox in August, and am not sure how to update or uninstall it.
Thanks,
Magnus
The text was updated successfully, but these errors were encountered:
@jeremy Thanks for your response, unfortunately it's not the solution.
The app is registered correctly, 2/3 of the requests (all to the same pow app/domain) go through correctly, whereas a few don't. It's not always the same resources that fail, some reloads they work, other times not.
I've just noticed that the issue appears when not running over https, (i.e. plain pow proxying a server) as well, but much less frequently, approximately 1/20. I will submit an issue there as well, as I do believe something is going on, triggering a temporary misconfiguration when too many requests happen concurrently.
In the meantime, would you be able to provide uninstallation instructions for powprox? I've looked around for them but can't find them.
Thanks for making powprox, it's made development easier for me. Unfortunately I'm currently running into some issues which I've traced down to powprox. I'm running osx 10.11.4.
Accessing the .dev domain with http it works, but with https some of the "later" resources (such as
@import
s in css files & images) fail with a 503 result. The images & css files aren't big (< 1MB), and there are only about 20 total requests, of which ~6 fail.I've updated the nginx config to write an error log, in which the following message matches requests returning 503:
an upstream response is buffered to a temporary file /usr/local/var/run/nginx/proxy_temp/1/16/0000000161 while reading upstream
. I tried applying various fixes I found online to no avail.The requests in question - I'm looking in the browser's network inspector - have the same request headers, but fewer response headers, specifically:
status: 503
,server: nginx/1.10.2
, date, content-type, andx-pow-template:application_not_found
. My guess is that the proxy configuration isn't setup to handle file buffered responses, but I'm not sure how to verify or resolve it.I installed powprox in August, and am not sure how to update or uninstall it.
Thanks,
Magnus
The text was updated successfully, but these errors were encountered: