Amazon Cloud : AWS Linux Server Tips, Tricks & Tutorials

Email forwarding option missing on newly setup google hosted domains I am using my company g suite account there I hosted my 2 domains. I’ve been using this for several domains, and I typically create an abc@my.domain.com account and have it forward all incoming emails to my personal email account. Usually you do this in Mail settings / Forwarding and POP/IMAP but recently this option disappeared on the the google hosted domains, there is only POP/IMAP Download instead. Solution : 1st login in Admin console https://admin.google.com/ Open Apps > G suite > Gmail [See image] Now open :     Advanced settings And enable it : Automatic forwarding in side End User Access : Changes will take some time to propagate to users(wait till 24 hours) Thanks for being here : Google hosted domains Forwarding and POP/IMAP but recently this option disappeared

Introduction :  USVN server   major  two error - 404 F orbidden - 500 Internal Error Occur :   1)  404 forbidden  Error during 1 st  time checkout SVN repo from USVN server After successfully installing the server USVN, if you receive the error 404 forbidden during the new SVN repo checkout Solution : Always add svn repo in project group. 2)  500 Internal Error in response to POST request for '/usvn/svn/test/!svn/me' 1 st  time commit After successful completion of the check svn repo folder. When it comes to commit your files on the SVN server, you will find error 500 Internal Solution :Make changes under the public folder’s htaccess. file location usvn/scr/public/.htaccess <Files *.ini> Order Allow,Deny Deny from all </Files> php_flag short_open_tag on php_flag magic_quotes_gpc off RewriteEngine on #RewriteCond RewriteBase "//usvn/" RewriteRule ^svn/ - [L,NC] #this is the rule I added to fix the 500 errors RewriteCond %{REQUEST...

Symptoms When visiting the website, it fails to load with error 521. The error occurs because the origin web server refused the connection from CloudFlare CloudFlare is used Website uses Nginx as a reverse-proxy; Cause CloudFlare IP addresses were blocked by  nginx  because of outdated contents of  /etc/nginx/conf.d/cloudflare.conf . /etc/nginx/conf.d/cloudflare.conf  contains old CloudFlare IP addresses list. Solution Make sure that you're not blocking CloudFlare IPs in  .htaccess ,  iptables , or your firewall. Make sure that you're operating off of the most recent versions of Bad Behavior or  mod_security . You want to ensure that mod_security's core rules aren't blocking CloudFlare requests; If you are running custom Apache modules, such as  mod_antiloris  and  mod_reqtimeout , disable and unload the modules. These modules will block any time an IP that connects more than 22 times. Since all connect...