network profile
| bio | website | kpthunder.com |
|---|---|---|
| location | United States | |
| age | 21 | |
| visits | member for | 2 years, 9 months |
| seen | May 2 at 14:19 | |
| stats | profile views | 23 |
Robble robble.
|
Apr 18 |
awarded | Autobiographer |
|
Feb 19 |
awarded | Popular Question |
|
Dec 20 |
awarded | Self-Learner |
|
Dec 18 |
awarded | Yearling |
|
Dec 15 |
awarded | Popular Question |
|
Dec 14 |
awarded | Notable Question |
|
Oct 17 |
accepted | Gitolite SSH URL Format |
|
Oct 16 |
asked | Gitolite SSH URL Format |
|
Jun 7 |
awarded | Popular Question |
|
May 16 |
comment |
UWSGI and NGINX for Python Apps on Ubuntu 11.10 Try listing the contents of /tmp (ls /tmp) after you restart uwsgi. If it's not there then check the uswsgi logs to see what's up. |
|
Dec 31 |
accepted | Tomcat Manager 403 Behind Nginx |
|
Dec 30 |
awarded | Commentator |
|
Dec 30 |
answered | Tomcat Manager 403 Behind Nginx |
|
Dec 30 |
comment |
Tomcat Manager 403 Behind Nginx I've figured out what's wrong and got it working thanks to your logging suggestion. I'll post an answer. |
|
Dec 30 |
comment |
Tomcat Manager 403 Behind Nginx Nothing that I can see. The only relevant information appears in the access logs. Where else should I look? |
|
Dec 30 |
comment |
Tomcat Manager 403 Behind Nginx Yes, I just opened up 8080 in the firewall and tried to access it directly by entering the username and password (admin, secret) into the prompt. Same result, 403. |
|
Dec 29 |
asked | Tomcat Manager 403 Behind Nginx |
|
Dec 27 |
accepted | Restrict User Access to Certain Ports |
|
Dec 26 |
comment |
Restrict User Access to Certain Ports Yes, I am aware of the ports below 1024. I would like to have more control over the ports higher than that as to avoid any possible conflicts e.g. somebody has something running on 9001 and takes it down momentarily -- meanwhile somebody else takes port 9001 for their own purpose. |
|
Dec 26 |
asked | Restrict User Access to Certain Ports |
