The OP has been updated with the latest example and updated to solve a twitter embed issue.
It took me forever to find out the issue. It was actually Microsoft 10 Edge which displayed the error which I researched online. That led me back to the vhost and those lines. For once a Microsoft browser was the solution to an issue... instead of the cause of one.
@eva2000 Does the gzip need to be included in the file? Someone on the IPB forum told me to remove it and I wanted to check with you. Is that included in another file or should I add it back to the vhost file? Thanks! Code: # GZIP static content not processed by IPB. gzip on; gzip_static on; gzip_http_version 1.1; gzip_vary on; gzip_comp_level 3; gzip_proxied any; gzip_types text/plain text/css application/json application/x-javascript application/xml application/xml+rss text/javascript application/javascript text/x-js; gzip_buffers 16 8k; gzip_disable "MSIE [1-6].(?!.*SV1)";
yes remove it as it's already enabled server wide in /usr/local/nginx/conf/nginx.conf in http {} context
Thank you! I will relay your response over there. I appreciate all the help! BTW... for the first time I actually enjoyed reading a newsletter. I never even knew I signed up for one, but thanks, it had some great information!
cheers I don't like spam myself but if it's bug or security related to Centmin Mod, i try to let end users know
Noticed two things with this config. Code: # Allow access to JS file location ~^/(applications/core/interface/js/js.php) { include /usr/local/nginx/conf/php.conf; allow all; } This does not seem to work and if you use the image proxy for ssl you also need to allow access to /applications/core/interface/imageproxy/imageproxy.php. I rewrote the rules as follows: Code: # Allow access to imageproxy location ^~ /applications/core/interface/imageproxy/imageproxy.php { include /usr/local/nginx/conf/php.conf; allow all; } # Allow access to JS file location ^~ /applications/core/interface/js/js.php { include /usr/local/nginx/conf/php.conf; allow all; } As a side note, I am not using the CODEB tag because it doesn't like spacing. @eva2000
Which is the correct way? The second one I'm using and works on my forum. Had to allow that so the block manager would work in the front-end. Code: location ^~ /applications/core/interface/js/js.php { include /usr/local/nginx/conf/php.conf; allow all; } or Code: location ~^/(applications/core/interface/js/js.php) { include /usr/local/nginx/conf/php.conf; allow all; }
This is correct. You can test it yourself by browsing to the file in your browser, if it returns a 403 error then your rule is not working.
I've noticed some other people having issues when IPB is inside another directory. There was a poster on the IPB forum putting IPB in "main" he was having all kinds of issues with the vhost file.
There was a poster on the IPB forum putting IPB in "main" he was having all kinds of issues with the vhost file.
I have mine in the root directory and everything is working for me. Why would it make a difference if it was in a sub-directory... hmm.