• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.


Search the Community

Showing results for tags 'reverse proxy'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • vpsBoard
    • Announcements & Contests
    • Industry News
  • Virtual Private Servers
    • General Talk
    • Operating a VPS Business
    • Tutorials and Guides
    • Questions and Answers
  • The Lounge
    • The Pub (Off topic discussion)
    • Coding, Scripting & Programming
    • SBC, ARM, Home Automation
  • Marketplace & Reviews
    • Reviews
    • VPS Offers
    • Other Offers
    • Service Requests

Found 3 results

  1. How to install vDDoS Protection - Reverse Proxy Layer 7 Firewall Filter Mitigate DOS, DDOS, SYN Floods, or HTTP Floods attack What is vDDoS Protection? vDDoS Protection is free software to provide a Reverse Proxy Server HTTP(S) protocols. It act as a Layer 7 Firewall Filter & Mitigate DOS, DDOS, SYN Floods, or HTTP Floods attack to protect your website. Features: -Reverse Proxy -DDoS Protection -Robot Mitigator -HTTP challenge/response -reCaptcha Robot challenge -HTTP Denial of Service tools -Cookie challenge/response -Block/Allow Country Code You Want (Status 403) -Limit the request connection coming from a single IP address (Status 503) -CDN Support (CloudFlare, Incapsula...) -Whitelist for Botsearch (SEO Support, Allow Botsearch: Google, Alexa, Bing, Yahoo, Yandex, Facebook...) How it work? vDDoS Protection is Nginx bundled with module HTTP/2; GeoIP; Limit Req, Testcookie; reCaptcha processor... Working like CloudFlare, but vDDoS is software help you build your own System Firewall. If your site does not use protection service: (accept all queries) If your site uses protection service: (challenge all queries) -Human queries: -Bad Bots queries: How to install vDDoS? -vDDoS Protection only support CentOS Server 5/6/7 x86_64 (http://centos.org) & CloudLinux Server 5/6/7 x86_64 (http://cloudlinux.com) -Please go to Homepage and download vDDoS Protection version working on your system (https://github.com/duy13/vDDoS-Protection) -vDDoS Protection should be installed before installing other things (cPanel, VestaCP, LAMP, LEMP...) yum -y install epel-release yum -y install curl wget gc gcc gcc-c++ pcre-devel zlib-devel make wget openssl-devel libxml2-devel libxslt-devel gd-devel perl-ExtUtils-Embed GeoIP-devel gperftools gperftools-devel libatomic_ops-devel perl-ExtUtils-Embed gcc automake autoconf apr-util-devel gc gcc gcc-c++ pcre-devel zlib-devel make wget openssl-devel libxml2-devel libxslt-devel gd-devel perl-ExtUtils-Embed GeoIP-devel gperftools gperftools-devel libatomic_ops-devel perl-ExtUtils-Embed Example: my system is CentOS 7 x86_64 install vDDoS 1.10.1 Version (only need wget a file vddos-1.10.1-centos7): curl -L https://github.com/duy13/vDDoS-Protection/raw/master/vddos-1.10.1-centos7 -o /usr/bin/vddos chmod 700 /usr/bin/vddos /usr/bin/vddos help /usr/bin/vddos setup (This installation takes about 15 minutes or more) vDDoS Command Line? Welcome to vDDoS, a HTTP(S) DDoS Protection Reverse Proxy. Thank you for using! Command Line Usage: vddos setup :installing vDDoS service for the first time into /vddos vddos start :start vDDoS service vddos stop :stop vDDoS service vddos restart :restart vDDoS service vddos autostart :auto-start vDDoS services on boot vddos attack :create a DDoS attacks to HTTP target (in 30 min) vddos stopattack :stop "vddos attack" command vddos help :display this help Please sure download vDDoS source from: vddos.voduy.com How to use vDDoS protect your website? Please edit your website.conf file in /vddos/conf.d Example Edit my website.conf: # nano /vddos/conf.d/website.conf # Website Listen Backend Cache Security SSL-Prikey SSL-CRTkey default no 200 no no your-domain.com no 200 no no default no 307 /vddos/ssl/your-domain.com.pri /vddos/ssl/your-domain.com.crt your-domain.com no 307 /vddos/ssl/your-domain.com.pri /vddos/ssl/your-domain.com.crt your-domain.com yes click /vddos/ssl/your-domain.com.pri /vddos/ssl/your-domain.com.crt "your-domain.com" is my site on my Apache backend want to be Protection by vDDoS "default" is option for All remaining sites /vddos/ssl/your-domain.com.pri is SSL Private key my website /vddos/ssl/your-domain.com.crt is SSL Public key my website Cache: variable: no, yes (Sets proxy cache website on vDDoS) Security: variable: no, 307, 200, click, 5s, high, captcha (Sets a valid for Security Level Protection) Note Security Level: no < 307 < 200 < click < 5s < high < captcha Restart vDDoS after saving: vddos restart Set Real IP traffic from Proxy or CDN: Please edit file cdn-ip.conf # nano /vddos/conf.d/cdn-ip.conf # Cloudflare set_real_ip_from; ... Deny Country or IP: Please edit file blacklist-countrycode.conf # nano /vddos/conf.d/blacklist-countrycode.conf geoip_country /usr/share/GeoIP/GeoIP.dat; map $geoip_country_code $allowed_country { default yes; US yes; CN no; } deny; Allow your IP Address do not need protection & challenge: Please edit file whitelist-botsearch.conf # nano /vddos/conf.d/whitelist-botsearch.conf #Alexa Bot IP Addresses;; ... Use Mode reCaptcha: Please edit file recaptcha-secretkey.conf & recaptcha-sitekey.conf # nano /vddos/conf.d/recaptcha-sitekey.conf # Website reCaptcha-sitekey (View KEY in https://www.google.com/recaptcha/admin#list) your-domain.com 6Lcr6QkUAAAAAxxxxxxxxxxxxxxxxxxxxxxxxxxx your-domain.org 6Lcr6FFFAAAAAxxxxxxxxxxxxxxxxxxxxxxxxxxx ... # nano /vddos/conf.d/recaptcha-secretkey.conf DEBUG=False RE_SECRETS = { 'your-domain.com': '6Lcr6QkUAAAAxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'your-domain.org': '6LcKngoUAAAAxxxxxxxxxxxxxxxxxxxxxxxxxxx' } (Go to https://www.google.com/recaptcha/admin#list and get your key for vDDoS) Recommend? -Recommend You use vDDoS with CloudFlare Free/Pro (hide your website real IP Address) (CloudFlare is Mitigate Firewall Layer 3-4) (vDDoS Protection is Mitigate Firewall Layer 7) -Download vDDoS Protection packages from vDDoS HomePages -Use this soft only for testing or demo attack! vDDoS Protection is Simple like that!
  2. Like most folks around here, I've been piled up with VPS accounts all over for years. VPS services are swell, but for me more than a few is a time sewer. Even the near instant provisioning of Digital Ocean gets a bit tiring and scripting things for a public exposed full server is just meh, stressful and moderate waste of my valuable time. I've long been a self hosted advocate. Over the years I've had good bandwidth to home and office and tended to host stuff in-house. Recent years I haven't, but indeed still good enough for many things I need to do. Even now I have piles of servers sitting here with tons of resources on the LAN. Sending stuff out to a datacenter is just, well, PITA. Colo sucks, renting dedis is blah blah potluck, VPS is glorified toy. Time + money, better things to burn it on. So I am headed back to localhost. You lads can keep your clouds in Cloudlandia, giving your data to random vendors of doom, transmitting everything up to mission control. But, there is always a but. Localhost is a lonely place. There are times when I may need to or want to public expose something there. Think for most of you, demo'ing some new code for client, sharing that meme, or a design for client or other development stuff. Historically self-hosting has involved beating a hole in your internet connection which probably lives on DHCP behind NAT or some other convoluted hell abstraction. So folks slap together with one of the random DNS meets DHCP mapping services. Some paid, some freemium. It's multiple pieces of garbage, bubblegum, and bailing wire slapped together. Border drug cartel have less obstacles to contend with to tunnel dope in. INTRODUCING PAGEKITE! "the fast, reliable localhost tunneling solution" "The fast, reliable way to make localhost part of the Web. PageKite makes local websites or SSH servers publicly accessible in mere seconds, and works with any computer and any Internet connection. It's also 100% Open Source. Source: https://pagekite.net/ In Linux land: curl -s https://pagekite.net/pk/ |sudo bash pagekite.py 80 yourname.pagekite.me At that point if you have server running on localhost on port 80, the world can reach it at: http://yourname.pagekite.me This supports other protocols too. For instance, you can expose SSH real simply too... And you can in one line expose multiple ports. They have pre-made packages for Debian available, see: https://pagekite.net/wiki/Howto/GNULinux/DebianPackage/ Simple eh? Now I am a recovering VPS time waster recovering with localhost therapy. VPS for me now is more well defined need where I need the bandwidth capacity or some strategic resource. General purpose computing, I'll run that in my own LAN cloud. We have clouds here, or a pile of servers like most of those sky dreamers selling me snakeoil prior. This also makes IPv4 quite a bit less important in the big picture. Yes, the domain *.pagekite.me is limiting. You can sign up for your own custom domain or since it's open debug how to run your instance entirely on say one of those VPS instances out in the wild of the internet aka Cloudlandia. Have fun with PageKite, it's my favorite new find. Hopefully, other folks here enjoy it and do some interesting things with it.
  3. Working on updating an old project and have random problem getting something working in nginx. Trying to do something like this: existing url: www.domain.com/page.asp ---> redirect "invisibly" to user to new url: www.domain.com/page.php (via nginx reverse proxy) I basically have a list of URLs that are getting one at a time replaced / rewrote (pages contain backend application scripting that is getting rewrote). So can't just do detect on the extension (.asp) and universally reverse proxy them. Anyone have some nginx love / config / tips on how to accomplish this? I also don't want the URLs changing since other pieces in public out there. URL provided by user needs to remain the same and all the magic needs to happen with Nginx and reverse proxy functionality. Thank you!