Tricon Garage driver Corey Heim won his fourth NASCAR Craftsman Truck Series race of 2024 at World Wide Technology Raceway.

Corey Heim dominates Gateway for fourth Truck Series win of 2024

Get the most recent info and news about Gateway on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Gateway

Veera, a rapidly growing internet browser, is now available in over 100 countries, delivering a seamless browsing experience alongside one of the most comprehensive Web3 ecosystems. With over 4 million users and a monthly active base of 1 million+, Veera is positioning itself at the forefront of the evolving decentralized internet. Built for the future of the internet, Veera is designed to make Web3 intuitive, accessible, and rewarding. By combining decentralized applications (dApps), digital wallets, tokenized rewards, and secure browsing into a single interface, Veera eliminates the complexity that has historically hindered Web3 adoption. Since its launch, Veera has scaled 4mn users in less than a year, with a monthly active user base of 1Mn+, a daily active user base of 100k+, and an average time spent of over 13mins per day. With web3 usage growing every single day, Veera is set to be a game-changer in this fast-evolving ecosystem. "We are super excited to take Veera to over 100 markets within the first year of launch. I’m super grateful to the team, our investors, and our user base for giving us this confidence. Our goal with Veera was to build a product that genuinely adds value to users’ lives. We have always been a gateway to the internet for our users—now, we’re also a comprehensive gateway to the world of Web3. We believe the future of the internet is decentralized, and Veera is designed to make that future accessible to everyone. We are conscious of the responsibility we have to provide the best possible experience to new users exploring web3 for the first time. And this is just the beginning. We have so much more in store for users across the world," said Arjun Ghose, Founder & CEO, Veera. “Veera isn’t just a browser; it’s a gateway to the decentralized world because it packs the power of a browser, crypto wallet, dapp store and immersive Web3 experiences into a single platform. Our mission is simple: empower users with a secure, privacy-focused, and rewarding Web3 experience. Our intuitive UX simplifies access to Web3 onboarding while preserving user autonomy, helping us shape the next era of the internet,” added Sukhdeep Bhogal, COO & CPO, Veera. Veera was envisioned as a Web3-native challenger browser by Arjun Ghose (former investor at Falcon Edge/Alpha Wave and McKinsey), Aditya Julka (serial entrepreneur, Founder of Paddle8, and entrepreneur-in-residence at Harvard Business School), and Kanu Gupta (founding leadership of Goldman Sachs in India, serial investor). Backed by leading investors including CMCC, 6th Man Ventures, Folius Ventures, Reflexive Ventures, Sfermion, Ayon Capital, COG Network, and iSeed Ventures, Veera is shaping the future of decentralized browsing and digital experiences. The company’s roadmap includes an upcoming iOS launch, further chain abstraction & support, referrals, single click swaps, etc., further strengthening Veera’s position as the definitive Web3 SuperApp for users worldwide. Website: https://veera.com/ Product Video - https://youtu.be/VAtEevBYuHc Veera, a rapidly growing internet browser, is now available in over 100 countries, delivering a seamless browsing experience alongside one of the most comprehensive Web3 ecosystems. With over 4 million users and a monthly active base of 1 million+, Veera is positioning itself at the forefront of the evolving decentralized internet. Built for the future of the internet, Veera is designed to make Web3 intuitive, accessible, and rewarding. By combining decentralized applications (dApps), digital wallets, tokenized rewards, and secure browsing into a single interface, Veera eliminates the complexity that has historically hindered Web3 adoption. Since its launch, Veera has scaled 4mn users in less than a year, with a monthly active user base of 1Mn+, a daily active user base of 100k+, and an average time spent of over 13mins per day. With web3 usage growing every single day, Veera is set to be a game-changer in this fast-evolving ecosystem. "We are super excited to take Veera to over 100 markets within the first year of launch. I’m super grateful to the team, our investors, and our user base for giving us this confidence. Our goal with Veera was to build a product that genuinely adds value to users’ lives. We have always been a gateway to the internet for our users—now, we’re also a comprehensive gateway to the world of Web3. We believe the future of the internet is decentralized, and Veera is designed to make that future accessible to everyone. We are conscious of the responsibility we have to provide the best possible experience to new users exploring web3 for the first time. And this is just the beginning. We have so much more in store for users across the world," said Arjun Ghose, Founder & CEO, Veera. “Veera isn’t just a browser; it’s a gateway to the decentralized world because it packs the power of a browser, crypto wallet, dapp store and immersive Web3 experiences into a single platform. Our mission is simple: empower users with a secure, privacy-focused, and rewarding Web3 experience. Our intuitive UX simplifies access to Web3 onboarding while preserving user autonomy, helping us shape the next era of the internet,” added Sukhdeep Bhogal, COO & CPO, Veera. Veera was envisioned as a Web3-native challenger browser by Arjun Ghose (former investor at Falcon Edge/Alpha Wave and McKinsey), Aditya Julka (serial entrepreneur, Founder of Paddle8, and entrepreneur-in-residence at Harvard Business School), and Kanu Gupta (founding leadership of Goldman Sachs in India, serial investor). Backed by leading investors including CMCC, 6th Man Ventures, Folius Ventures, Reflexive Ventures, Sfermion, Ayon Capital, COG Network, and iSeed Ventures, Veera is shaping the future of decentralized browsing and digital experiences. The company’s roadmap includes an upcoming iOS launch, further chain abstraction & support, referrals, single click swaps, etc., further strengthening Veera’s position as the definitive Web3 SuperApp for users worldwide. Website: https://veera.com/ https://veera.com/ Product Video - https://youtu.be/VAtEevBYuHc https://youtu.be/VAtEevBYuHc

100+ Markets and Counting - Veera Becomes the Ultimate Gateway to Web3

100+ Markanaka ukat Jakhuwi - Veera ukax Web3 ukar Qhipa Punkuruw tuku

100+ tržišta i brojanje - Veera postaje ultimativni pristup Web3

100+ markeder og tæller - Veera bliver den ultimative gateway til Web3

100+ αγορές και καταμέτρηση - Η Veera γίνεται η απόλυτη πύλη στο Web3

Más de 100 mercados y seguimos sumando: Veera se convierte en la puerta de entrada definitiva a la Web3

100+ Merkatu eta zenbatzen - Veera Web3rako azken ataria bihurtzen da

100+ piac és számlálás – Veera a Web3 végső kapuja

100+ շուկաներ և հաշվում – Veera-ն դառնում է Web3-ի վերջնական դարպասը

100以上の市場とカウント - VeeraはWeb3への究極のゲートウェイになります

100+ бозорҳо ва ҳисобкунӣ - Veera дарвозаи ниҳоии Web3 мегардад

100+ Markets at Nagbibilang - Naging Ultimate Gateway sa Web3 si Veera

100+ ринків і їх кількість зростає - Veera стає найкращим шлюзом для Web3

Mark Your Calendars: February 14, 2025 We’re thrilled to announce that TapSwap, the world’s first Web3 skill-gaming platform, is taking a giant leap forward with its listing on Bitget on February 14, 2025. This milestone marks an exciting new chapter in our journey, reinforcing our commitment to building a sustainable and rewarding gaming ecosystem for millions of players worldwide. TapSwap: Where Skill Meets Crypto Unlike traditional play-to-earn models that rely on luck or monotonous grinding, TapSwap is all about skill-based gaming. Players are rewarded for their mastery and competitive edge rather than chance, creating a truly meritocratic environment where skill determines success. With a transparent blockchain-powered system, we ensure fair play, real earning opportunities, and a thriving economy centred around our native TAPS token. With over 72 million total users, 3 million daily active users (DAU), and 10 million weekly active users (WAU), TapSwap has quickly grown into one of the most active Web3 gaming communities. Whether you're a casual gamer or an esports competitor, TapSwap offers a platform where you can compete, earn, and engage in a decentralized gaming experience like never before. The Power of the TAPS Token At the core of TapSwap’s ecosystem is the TAPS token, designed to power the platform’s economy and provide multiple avenues for user engagement, including: Tournament Participation: Enter skill-based tournaments with TAPS and compete for substantial rewards.
Fight2Earn: A high-stakes mode where players battle for TAPS rewards based purely on skill.
Staking & Passive Income: Users can stake TAPS to earn rewards while contributing to the ecosystem’s stability.
Governance: Token holders influence platform decisions, shaping the future of TapSwap.
In-Game Purchases & Premium Access: Enhance your gaming experience with exclusive skins, avatars, and premium accounts. Why the Bitget Listing Matters Our listing on Bitget, a leading cryptocurrency exchange, is a major step toward long-term success for TapSwap and its growing community. This listing: Boosts TAPS liquidity and accessibility
Opens doors for new investors and gamers
Strengthens TapSwap’s position in the Web3 gaming market
Creates more opportunities for the TapSwap community to grow and thrive By listing on Bitget, we’re not just increasing the reach of the TAPS token—we’re creating a gateway for millions of users to join the TapSwap movement and benefit from a truly skill-based gaming economy. GATE OPPORTUNITY: Don’t Miss Out With the Bitget listing right around the corner, now is the perfect time to get involved in TapSwap’s ecosystem. Whether you’re a gamer, investor, or blockchain enthusiast, this is your chance to be part of a revolutionary Web3 gaming platform. 🚨 BIG NEWS FOR THE TAPSWAP COMMUNITY! 🚨 All TapSwap community members have just received 10 tickets in the TapSwap mini-app! 🎟️ These tickets are your FREE entry to the BIG GAME happening at the launch of our Web3 skill gaming platform! 🕹️🔥 🏆 $1 MILLION PRIZE POOL—for the winners of this epic competition! 💰💎 Didn’t participate in the TapSwap app? No worries—you’ll still have the chance to buy tickets and join the game! The future of skill-based gaming is here, and we’re just getting started. TapSwap is one of the first tap-to-earn projects that is transforming into a full-fledged gaming platform. Invest, play, and win with TapSwap! Read the full details about our Bitget listing and how you can participate in the $1M prize pool! This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here Mark Your Calendars: February 14, 2025 We’re thrilled to announce that TapSwap, the world’s first Web3 skill-gaming platform, is taking a giant leap forward with its listing on Bitget on February 14, 2025. This milestone marks an exciting new chapter in our journey, reinforcing our commitment to building a sustainable and rewarding gaming ecosystem for millions of players worldwide. TapSwap: Where Skill Meets Crypto Unlike traditional play-to-earn models that rely on luck or monotonous grinding, TapSwap is all about skill-based gaming . Players are rewarded for their mastery and competitive edge rather than chance, creating a truly meritocratic environment where skill determines success. skill-based gaming skill-based gaming With a transparent blockchain-powered system, we ensure fair play, real earning opportunities, and a thriving economy centred around our native TAPS token. With over 72 million total users, 3 million daily active users (DAU), and 10 million weekly active users (WAU), TapSwap has quickly grown into one of the most active Web3 gaming communities. Whether you're a casual gamer or an esports competitor, TapSwap offers a platform where you can compete, earn, and engage in a decentralized gaming experience like never before. The Power of the TAPS Token At the core of TapSwap’s ecosystem is the TAPS token, designed to power the platform’s economy and provide multiple avenues for user engagement, including: Tournament Participation: Enter skill-based tournaments with TAPS and compete for substantial rewards. Fight2Earn: A high-stakes mode where players battle for TAPS rewards based purely on skill. Staking & Passive Income: Users can stake TAPS to earn rewards while contributing to the ecosystem’s stability. Governance: Token holders influence platform decisions, shaping the future of TapSwap. In-Game Purchases & Premium Access: Enhance your gaming experience with exclusive skins, avatars, and premium accounts. Tournament Participation: Enter skill-based tournaments with TAPS and compete for substantial rewards. Fight2Earn: A high-stakes mode where players battle for TAPS rewards based purely on skill. Staking & Passive Income: Users can stake TAPS to earn rewards while contributing to the ecosystem’s stability. Governance: Token holders influence platform decisions, shaping the future of TapSwap. In-Game Purchases & Premium Access: Enhance your gaming experience with exclusive skins, avatars, and premium accounts. Why the Bitget Listing Matters Our listing on Bitget, a leading cryptocurrency exchange, is a major step toward long-term success for TapSwap and its growing community. This listing: Boosts TAPS liquidity and accessibility Opens doors for new investors and gamers Strengthens TapSwap’s position in the Web3 gaming market Creates more opportunities for the TapSwap community to grow and thrive Boosts TAPS liquidity and accessibility Opens doors for new investors and gamers Strengthens TapSwap’s position in the Web3 gaming market Creates more opportunities for the TapSwap community to grow and thrive By listing on Bitget, we’re not just increasing the reach of the TAPS token—we’re creating a gateway for millions of users to join the TapSwap movement and benefit from a truly skill-based gaming economy. GATE OPPORTUNITY: Don’t Miss Out With the Bitget listing right around the corner, now is the perfect time to get involved in TapSwap’s ecosystem. Whether you’re a gamer, investor, or blockchain enthusiast, this is your chance to be part of a revolutionary Web3 gaming platform. 🚨 BIG NEWS FOR THE TAPSWAP COMMUNITY! 🚨 All TapSwap community members have just received 10 tickets in the TapSwap mini-app! 🎟️ These tickets are your FREE entry to the BIG GAME happening at the launch of our Web3 skill gaming platform! 🕹️🔥 🏆 $1 MILLION PRIZE POOL—for the winners of this epic competition! 💰💎 Didn’t participate in the TapSwap app? No worries—you’ll still have the chance to buy tickets and join the game! The future of skill-based gaming is here, and we’re just getting started. TapSwap is one of the first tap-to-earn projects that is transforming into a full-fledged gaming platform. Invest, play, and win with TapSwap! Read the full details about our Bitget listing and how you can participate in the $1M prize pool! participate in the $1M prize pool! participate in the $1M prize pool! This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Btcwire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

TapSwap To Be Listed On Bitget: A Gateway To Long-Term Success

TikSwap om op Bitget gelys te word: 'n Poort na langtermynsukses

TapSwap být uveden na Bitget: Brána k dlouhodobému úspěchu

TapSwap για να εισαχθεί στο Bitget: Μια πύλη για τη μακροπρόθεσμη επιτυχία

TapSwap se incorporará a Bitget: una puerta de entrada al éxito a largo plazo

TapSwap כדי להירשם ב-Bitget: שער להצלחה ארוכת טווח

TapSwap će biti uvršten na Bitget: Put do dugoročnog uspjeha

TapSwap Akan Terdaftar di Bitget: Gerbang Menuju Kesuksesan Jangka Panjang

TapSwap が Bitget に上場: 長期的な成功への入り口

TapSwap за да биде наведен на Bitget: Порта за долгорочен успех

TapSwap будет добавлен на Bitget: путь к долгосрочному успеху

TapSwap byť uvedený na Bitget: Brána k dlhodobému úspechu

ТапСвап ће бити уврштен на Битгет: капија за дугорочни успех

A Strange Yucca Tribute Concert: Configuring Kong API Gateway With Micronaut Services in Kotlin 

A Single Point of Access or Chaos — Unlocking Non-Blocking API Gateways

When browsing the web, you may occasionally encounter an error message that reads, "504 Gateway Timeout." While it might seem cryptic at first, this error is more common than you think. If you're wondering what it is, why it happens, and how to fix it, this guide has got you covered. What Is a 504 Gateway Timeout Error? A 504 Gateway Timeout Error occurs when a server acting as a gateway or proxy doesn't receive a timely response from an upstream server. In simpler terms, it means the server you're trying to access is taking too long to respond. This error is a part of the HTTP status code family, which communicates the state of your connection to a server. A "504" indicates that the server acting as an intermediary (like a web host or content delivery network) could not complete your request because the upstream server is unresponsive. What Causes a 504 Gateway Timeout Error? Understanding the causes of this error is key to troubleshooting. Here are the most common reasons: 1. Server Overload The upstream server is overwhelmed with traffic or resource demands. Websites experiencing sudden surges in visitors (e.g., during sales or viral events) often encounter this issue. 2. Poor Server Communication The gateway server and upstream server fail to communicate properly due to misconfigured settings or network interruptions. 3. DNS Issues If DNS (Domain Name System) records are outdated or misconfigured, servers might fail to locate each other. 4. Firewall Restrictions Firewalls may block requests from a specific IP address, thinking it's malicious, causing communication breakdowns. 5. Server Timeout Settings If the timeout period for a server request is too short, slower upstream servers may not respond in time, triggering a 504 error. How to Fix a 504 Gateway Timeout Error Fixing this error depends on whether you're a website visitor or the owner of the website. For Website Visitors: Refresh the Page


Sometimes, a temporary issue on the server resolves itself. Refreshing can help.



Check Your Internet Connection


Ensure your connection is stable. Disconnect and reconnect to verify.



Try Another Browser or Device


Use a different browser or device to rule out local issues.



Clear Your Browser Cache


Cached files can sometimes cause errors. Clear your cache and cookies.



Check if the Website Is Down

Use a tool like CheckIfWebsiteDown to confirm if the issue is global. For Website Owners or Administrators: Check Server Logs


Analyze server logs to identify where the communication breakdown occurred.



Restart Your Servers


Restarting the gateway or upstream server may resolve temporary glitches.



Update DNS Records


Ensure your DNS records are updated and correctly configured.



Increase Timeout Limits


Extend timeout periods in your server settings to allow upstream servers more time to respond.



Optimize Server Performance


Use load balancers or upgrade your hosting plan to handle more traffic efficiently.



Disable Firewall or Proxy Blocks


Review firewall rules to ensure legitimate requests aren’t being blocked.



Contact Your Hosting Provider

If the issue persists, reach out to your hosting provider for support. Preventing 504 Gateway Timeout Errors Proactive measures can help prevent future occurrences. Here’s what you can do: Monitor Server Health: Regularly check your servers for high resource usage or connectivity issues.
Use a Content Delivery Network (CDN): CDNs can distribute traffic and reduce server strain.
Optimize Your Website: Minimize heavy scripts and ensure faster loading times.
Conduct Regular DNS Checks: Keep DNS records updated and resolve any configuration errors promptly. Common Variations of the 504 Error Depending on the browser or server, the error message might look different: "HTTP 504 Gateway Timeout"
"504 Error – The server didn't respond in time"
"504 Gateway Timeout – nginx"
"Gateway Timeout Error – Cloudflare" While the phrasing varies, the issue remains the same: delayed communication between servers. When Should You Seek Professional Help? If you've tried the above fixes and still experience the error frequently, it’s time to consult a professional. Persistent 504 errors could indicate underlying server misconfigurations or hardware issues requiring expert attention. For website visitors, if the error persists on multiple devices and browsers, contact the website owner or administrator. Key Takeaways A 504 Gateway Timeout Error occurs when servers fail to communicate within a set timeframe.
Causes range from server overload to DNS misconfigurations.
Fixes include refreshing the page, checking DNS settings, and optimizing server performance.
Regular monitoring and proactive measures can prevent these errors from happening frequently. The 504 Gateway Timeout Error may seem daunting, but with a clear understanding and the right troubleshooting steps, you can resolve it efficiently. Whether you're a visitor encountering the error or a website owner managing traffic, this guide equips you with actionable solutions to tackle the issue. When browsing the web, you may occasionally encounter an error message that reads, "504 Gateway Timeout." While it might seem cryptic at first, this error is more common than you think. If you're wondering what it is, why it happens, and how to fix it, this guide has got you covered. What Is a 504 Gateway Timeout Error? What Is a 504 Gateway Timeout Error? A 504 Gateway Timeout Error occurs when a server acting as a gateway or proxy doesn't receive a timely response from an upstream server. In simpler terms, it means the server you're trying to access is taking too long to respond. This error is a part of the HTTP status code family, which communicates the state of your connection to a server. A "504" indicates that the server acting as an intermediary (like a web host or content delivery network) could not complete your request because the upstream server is unresponsive. What Causes a 504 Gateway Timeout Error? Understanding the causes of this error is key to troubleshooting. Here are the most common reasons: 1. Server Overload The upstream server is overwhelmed with traffic or resource demands. The upstream server is overwhelmed with traffic or resource demands. Websites experiencing sudden surges in visitors (e.g., during sales or viral events) often encounter this issue. Websites experiencing sudden surges in visitors (e.g., during sales or viral events) often encounter this issue. 2. Poor Server Communication The gateway server and upstream server fail to communicate properly due to misconfigured settings or network interruptions. The gateway server and upstream server fail to communicate properly due to misconfigured settings or network interruptions. 3. DNS Issues If DNS (Domain Name System) records are outdated or misconfigured, servers might fail to locate each other. If DNS (Domain Name System) records are outdated or misconfigured, servers might fail to locate each other. 4. Firewall Restrictions Firewalls may block requests from a specific IP address, thinking it's malicious, causing communication breakdowns. Firewalls may block requests from a specific IP address, thinking it's malicious, causing communication breakdowns. 5. Server Timeout Settings If the timeout period for a server request is too short, slower upstream servers may not respond in time, triggering a 504 error. Settings If the timeout period for a server request is too short, slower upstream servers may not respond in time, triggering a 504 error. How to Fix a 504 Gateway Timeout Error How to Fix a 504 Gateway Timeout Error Fixing this error depends on whether you're a website visitor or the owner of the website. For Website Visitors: For Website Visitors: Refresh the Page


Sometimes, a temporary issue on the server resolves itself. Refreshing can help. Check Your Internet Connection


Ensure your connection is stable. Disconnect and reconnect to verify. Try Another Browser or Device


Use a different browser or device to rule out local issues. Clear Your Browser Cache


Cached files can sometimes cause errors. Clear your cache and cookies. Check if the Website Is Down

Use a tool like CheckIfWebsiteDown to confirm if the issue is global. Refresh the Page Sometimes, a temporary issue on the server resolves itself. Refreshing can help. Refresh the Page Sometimes, a temporary issue on the server resolves itself. Refreshing can help. Sometimes, a temporary issue on the server resolves itself. Refreshing can help. Sometimes, a temporary issue on the server resolves itself. Refreshing can help. Check Your Internet Connection Ensure your connection is stable. Disconnect and reconnect to verify. Check Your Internet Connection Ensure your connection is stable. Disconnect and reconnect to verify. Ensure your connection is stable. Disconnect and reconnect to verify. Ensure your connection is stable. Disconnect and reconnect to verify. Try Another Browser or Device Use a different browser or device to rule out local issues. Try Another Browser or Device Use a different browser or device to rule out local issues. Use a different browser or device to rule out local issues. Use a different browser or device to rule out local issues. Clear Your Browser Cache Cached files can sometimes cause errors. Clear your cache and cookies. Clear Your Browser Cache Cached files can sometimes cause errors. Clear your cache and cookies. Cached files can sometimes cause errors. Clear your cache and cookies. Cached files can sometimes cause errors. Clear your cache and cookies. Check if the Website Is Down Use a tool like CheckIfWebsiteDown to confirm if the issue is global. Check if the Website Is Down Use a tool like CheckIfWebsiteDown to confirm if the issue is global. Use a tool like CheckIfWebsiteDown to confirm if the issue is global. CheckIfWebsiteDown For Website Owners or Administrators: For Website Owners or Administrators: Check Server Logs


Analyze server logs to identify where the communication breakdown occurred. Restart Your Servers


Restarting the gateway or upstream server may resolve temporary glitches. Update DNS Records


Ensure your DNS records are updated and correctly configured. Increase Timeout Limits


Extend timeout periods in your server settings to allow upstream servers more time to respond. Optimize Server Performance


Use load balancers or upgrade your hosting plan to handle more traffic efficiently. Disable Firewall or Proxy Blocks


Review firewall rules to ensure legitimate requests aren’t being blocked. Contact Your Hosting Provider

If the issue persists, reach out to your hosting provider for support. Check Server Logs Analyze server logs to identify where the communication breakdown occurred. Check Server Logs Analyze server logs to identify where the communication breakdown occurred. Analyze server logs to identify where the communication breakdown occurred. Analyze server logs to identify where the communication breakdown occurred. Restart Your Servers Restarting the gateway or upstream server may resolve temporary glitches. Restart Your Servers Restarting the gateway or upstream server may resolve temporary glitches. Restarting the gateway or upstream server may resolve temporary glitches. Restarting the gateway or upstream server may resolve temporary glitches. Update DNS Records Ensure your DNS records are updated and correctly configured. Update DNS Records Ensure your DNS records are updated and correctly configured. Ensure your DNS records are updated and correctly configured. Ensure your DNS records are updated and correctly configured. Increase Timeout Limits Extend timeout periods in your server settings to allow upstream servers more time to respond. Increase Timeout Limits Extend timeout periods in your server settings to allow upstream servers more time to respond. Extend timeout periods in your server settings to allow upstream servers more time to respond. Extend timeout periods in your server settings to allow upstream servers more time to respond. Optimize Server Performance Use load balancers or upgrade your hosting plan to handle more traffic efficiently. Optimize Server Performance Use load balancers or upgrade your hosting plan to handle more traffic efficiently. Use load balancers or upgrade your hosting plan to handle more traffic efficiently. Use load balancers or upgrade your hosting plan to handle more traffic efficiently. Disable Firewall or Proxy Blocks Review firewall rules to ensure legitimate requests aren’t being blocked. Disable Firewall or Proxy Blocks Review firewall rules to ensure legitimate requests aren’t being blocked. Review firewall rules to ensure legitimate requests aren’t being blocked. Review firewall rules to ensure legitimate requests aren’t being blocked. Contact Your Hosting Provider If the issue persists, reach out to your hosting provider for support. Contact Your Hosting Provider If the issue persists, reach out to your hosting provider for support. If the issue persists, reach out to your hosting provider for support. Preventing 504 Gateway Timeout Errors Preventing 504 Gateway Timeout Errors Proactive measures can help prevent future occurrences. Here’s what you can do: Monitor Server Health: Regularly check your servers for high resource usage or connectivity issues. Use a Content Delivery Network (CDN): CDNs can distribute traffic and reduce server strain. Optimize Your Website: Minimize heavy scripts and ensure faster loading times. Conduct Regular DNS Checks: Keep DNS records updated and resolve any configuration errors promptly. Monitor Server Health: Regularly check your servers for high resource usage or connectivity issues. Monitor Server Health: Use a Content Delivery Network (CDN): CDNs can distribute traffic and reduce server strain. Use a Content Delivery Network (CDN): Optimize Your Website: Minimize heavy scripts and ensure faster loading times. Optimize Your Website: Conduct Regular DNS Checks: Keep DNS records updated and resolve any configuration errors promptly. Conduct Regular DNS Checks: Common Variations of the 504 Error Common Variations of the 504 Error Depending on the browser or server, the error message might look different: "HTTP 504 Gateway Timeout" "504 Error – The server didn't respond in time" "504 Gateway Timeout – nginx" "Gateway Timeout Error – Cloudflare" "HTTP 504 Gateway Timeout" "HTTP 504 Gateway Timeout" "504 Error – The server didn't respond in time" "504 Error – The server didn't respond in time" "504 Gateway Timeout – nginx" "504 Gateway Timeout – nginx" "Gateway Timeout Error – Cloudflare" "Gateway Timeout Error – Cloudflare" While the phrasing varies, the issue remains the same: delayed communication between servers. When Should You Seek Professional Help? When Should You Seek Professional Help? If you've tried the above fixes and still experience the error frequently, it’s time to consult a professional. Persistent 504 errors could indicate underlying server misconfigurations or hardware issues requiring expert attention. For website visitors, if the error persists on multiple devices and browsers, contact the website owner or administrator. Key Takeaways Key Takeaways A 504 Gateway Timeout Error occurs when servers fail to communicate within a set timeframe. Causes range from server overload to DNS misconfigurations. Fixes include refreshing the page, checking DNS settings, and optimizing server performance. Regular monitoring and proactive measures can prevent these errors from happening frequently. A 504 Gateway Timeout Error occurs when servers fail to communicate within a set timeframe. Causes range from server overload to DNS misconfigurations. Fixes include refreshing the page, checking DNS settings, and optimizing server performance. Regular monitoring and proactive measures can prevent these errors from happening frequently. The 504 Gateway Timeout Error may seem daunting, but with a clear understanding and the right troubleshooting steps, you can resolve it efficiently. Whether you're a visitor encountering the error or a website owner managing traffic, this guide equips you with actionable solutions to tackle the issue.

What Is a 504 Gateway Timeout Error? Causes, Fixes, and Prevention

Kerberoasting: A Gateway to Privilege Escalation in Enterprise Networks

Cryptix.io, a trailblazer in cryptocurrency payment processing, announces its strategic expansion into the European market, poised to transform how businesses handle digital payments. Redefining Crypto Payment Standards With a proven track record of over three years in the industry, Cryptix has established itself as a trusted partner for online businesses globally. The company’s entry into Europe marks a significant milestone, offering advanced crypto payment solutions tailored to the needs of European enterprises. By seamlessly converting digital assets into fiat currencies or stablecoins, Cryptix is set to become a vital player in the region’s digital economy. A Global Vision with Local Benefits Cryptix’s expansion isn’t just about geographical growth; it’s about inclusivity and adaptability in the rapidly evolving world of digital finance. Alongside support for EUR and USD, Cryptix now accommodates MXN (Mexican Peso), BRL (Brazilian Real), and COP (Colombian Peso), reflecting its commitment to serving a diverse clientele. European businesses can now tap into broader markets with ease, leveraging Cryptix’s ability to facilitate transactions in multiple currencies. Streamlined Integration and User Experience What sets Cryptix apart is its focus on simplicity and efficiency. Businesses can integrate Cryptix into their operations via API or HTML iFrame, ensuring a smooth setup process. For those seeking a no-code solution, Cryptix offers an intuitive payment link generation feature, enabling swift transactions without the need for technical expertise. The comprehensive dashboard provided by Cryptix consolidates all essential functions into a single interface—managing conversions, top-ups, transaction histories, mass payouts, and withdrawals has never been easier. To combat the volatility inherent in cryptocurrency markets, Cryptix’s auto-conversion feature instantly converts crypto payments into stablecoins or fiat currencies, shielding businesses from exchange rate fluctuations**.** Unrivaled Value Proposition As Cryptix enters the European market, it does so with a clear value proposition: unparalleled transaction limits and minimal fees. Businesses can process up to $10,000 in transactions without requiring Know Your Business (KYB) verification. Upon verification, the sky's the limit—literally, with no upper cap on transaction volumes. Cryptix’s fee structure is another game-changer. With no charges for cryptocurrency top-ups or crypto-to-crypto exchanges, and a 0% fee for crypto-to-fiat conversions, the platform is among the most cost-effective in the industry. A modest 0.4% fee for accepting crypto payments and a 0.6% fee for fiat settlements further underscores Cryptix’s commitment to offering businesses a competitive edge in a burgeoning market. Positioning for the Future Cryptix’s European expansion signals more than just growth—it’s a bold statement of intent. As businesses across the continent grapple with the complexities of digital finance, Cryptix is set to provide them with the tools they need to thrive. By reducing barriers to entry and ensuring cost-effectiveness, Cryptix is not only entering the European market but is set to dominate it. For inquiries, please reach out at contact@cryptix.io About Cryptix.io Cryptix remains at the forefront of compliance, adhering strictly to Counterterrorism Financing (CTF) and Anti-Money Laundering (AML) regulations. Registered with the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC), Cryptix ensures the highest standards of safety and integrity in its operations. Committed to supporting small and medium-sized enterprises (SMEs), Cryptix empowers businesses to harness the potential of digital currencies, driving economic growth across regions. Cryptix.io, a trailblazer in cryptocurrency payment processing, announces its strategic expansion into the European market, poised to transform how businesses handle digital payments. Cryptix.io, a trailblazer in cryptocurrency payment processing, announces its strategic expansion into the European market, poised to transform how businesses handle digital payments. Cryptix.io, a trailblazer in cryptocurrency payment processing, announces its strategic expansion into the European market, poised to transform how businesses handle digital payments. Redefining Crypto Payment Standards Redefining Crypto Payment Standards With a proven track record of over three years in the industry, Cryptix has established itself as a trusted partner for online businesses globally. The company’s entry into Europe marks a significant milestone, offering advanced crypto payment solutions tailored to the needs of European enterprises. By seamlessly converting digital assets into fiat currencies or stablecoins, Cryptix is set to become a vital player in the region’s digital economy. A Global Vision with Local Benefits A Global Vision with Local Benefits Cryptix’s expansion isn’t just about geographical growth; it’s about inclusivity and adaptability in the rapidly evolving world of digital finance. Alongside support for EUR and USD, Cryptix now accommodates MXN (Mexican Peso), BRL (Brazilian Real), and COP (Colombian Peso), reflecting its commitment to serving a diverse clientele. European businesses can now tap into broader markets with ease, leveraging Cryptix’s ability to facilitate transactions in multiple currencies. Streamlined Integration and User Experience Streamlined Integration and User Experience What sets Cryptix apart is its focus on simplicity and efficiency. Businesses can integrate Cryptix into their operations via API or HTML iFrame, ensuring a smooth setup process. For those seeking a no-code solution, Cryptix offers an intuitive payment link generation feature, enabling swift transactions without the need for technical expertise. The comprehensive dashboard provided by Cryptix consolidates all essential functions into a single interface—managing conversions, top-ups, transaction histories, mass payouts, and withdrawals has never been easier. To combat the volatility inherent in cryptocurrency markets, Cryptix’s auto-conversion feature instantly converts crypto payments into stablecoins or fiat currencies, shielding businesses from exchange rate fluctuations**.** Unrivaled Value Proposition Unrivaled Value Proposition As Cryptix enters the European market, it does so with a clear value proposition: unparalleled transaction limits and minimal fees. Businesses can process up to $10,000 in transactions without requiring Know Your Business (KYB) verification. Upon verification, the sky's the limit—literally, with no upper cap on transaction volumes. Cryptix’s fee structure is another game-changer. With no charges for cryptocurrency top-ups or crypto-to-crypto exchanges, and a 0% fee for crypto-to-fiat conversions, the platform is among the most cost-effective in the industry. A modest 0.4% fee for accepting crypto payments and a 0.6% fee for fiat settlements further underscores Cryptix’s commitment to offering businesses a competitive edge in a burgeoning market. Positioning for the Future Positioning for the Future Cryptix’s European expansion signals more than just growth—it’s a bold statement of intent. As businesses across the continent grapple with the complexities of digital finance, Cryptix is set to provide them with the tools they need to thrive. By reducing barriers to entry and ensuring cost-effectiveness, Cryptix is not only entering the European market but is set to dominate it. For inquiries, please reach out at contact@cryptix.io For inquiries, please reach out at contact@cryptix.io contact@cryptix.io contact@cryptix.io About Cryptix.io About Cryptix.io Cryptix remains at the forefront of compliance, adhering strictly to Counterterrorism Financing (CTF) and Anti-Money Laundering (AML) regulations. Registered with the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC), Cryptix ensures the highest standards of safety and integrity in its operations. Committed to supporting small and medium-sized enterprises (SMEs), Cryptix empowers businesses to harness the potential of digital currencies, driving economic growth across regions. Cryptix Cryptix

Cryptix Revolutionizes Crypto Payments in Europe with Innovative Gateway Solutions

Cryptix ukax Europa uksanx Crypto Payllawinakx Revolucionawayiwa, Innovative Gateway Solutions ukampi

Cryptix revoluciona los pagos con criptomonedas en Europa con soluciones de pasarela innovadoras

A Cryptix innovatív átjárómegoldásaival forradalmasítja a kriptográfiai fizetéseket Európában

Cryptix は革新的なゲートウェイ ソリューションでヨーロッパの暗号通貨決済に革命を起こします

Cryptix Европадагы крипто төлөмдөрүн инновациялык шлюз чечимдери менен өзгөртөт

Cryptix revoluționează plățile cripto în Europa cu soluții inovatoare de gateway

Цриптик револуционише крипто плаћања у Европи са иновативним решењима мрежног пролаза

Cryptix бо ҳалли инноватсионии Gateway пардохтҳои криптоиро дар Аврупо инқилоб мекунад

Cryptix ปฏิวัติการชำระเงินด้วย Crypto ในยุโรปด้วยโซลูชันเกตเวย์ที่สร้างสรรค์

Cryptix революціонізує криптовалютні платежі в Європі за допомогою інноваційних рішень для шлюзу

I-Cryptix iguqula iiNtlawulo ze-Crypto eYurophu kunye ne-Innovative Gateway Solutions

In my talk, “Evolving your APIs,” I mention that an API gateway is a Reverse Proxy "on steroids.” One key difference between the former and the latter is that the API Gateway is not unfriendly to business logic. The poster child is rate-limiting. Rate-limiting is an age-old Reverse Proxy feature focused on protecting against Distributed Denial of Service (DDoS) attacks. It treats all clients the same and is purely technical. In this day and age, most API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It's not technical anymore and requires to differentiate between clients. In this post, I want to detail how to do it with Apache APISIX. Note I take most of the material from the workshop. Rate-limiting for the masses Apache APISIX offers no less than three plugins to rate limit requests: limit conn: limits the number of concurrent requests
limit req: limits the number of requests based on the Leaky Bucket algorithm
limit count: limits the number of requests based on a fixed time window The limit-count plugin is a good candidate for this post. Let's configure the plugin for a route: routes:
  - uri: /get
    upstream:
      nodes:
        "http://httpbin.org:80": 1
    plugins:
      limit-count:                     #1
        count: 1                       #2
        time_window: 60                #2
        rejected_code: 429             #3
#END Set the limit-count plugin
Limit requests to one every 60 seconds
Override the default HTTP response code, i.e., 503 At this point, we configured regular rate limiting. curl -v http://localhost:9080/get
curl -v http://localhost:9080/get If we execute the second request before a minute has passed, the result is the following: HTTP/1.1 429 Too Many Requests
Date: Tue, 09 Jul 2024 06:55:07 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 241
Connection: keep-alive
X-RateLimit-Limit: 1                   #1
X-RateLimit-Remaining: 0               #2
X-RateLimit-Reset: 59                  #3
Server: APISIX/3.9.1

<html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<hr><center>openresty</center>
<p><em>Powered by <a href="https://apisix.apache.org/">APISIX</a>.</em></p></body>
</html> Configured limit
Remaining quota
Waiting time in seconds before quota replenishment Per-consumer rate limiting To configure per-consumer rate limiting, we first need to implement request authentication. APISIX offers many authentication plugins; we shall use the simplest one, key-auth. key-auth checks a specific HTTP request header - apikey by default. Here's how we configure consumers: consumers:
  - username: johndoe                  #1
    plugins:
      key-auth:
        key: john                      #2
  - username: janedoe                  #1
    plugins:
      key-auth:
        key: jane                      #2 Users
HTTP header request value curl -H 'apikey: john' localhost:9080/get #1
curl -H 'apikey: jane' localhost:9080/get #2 Authenticate as johndoe
Authenticate as janedoe In general, you attach plugins to APISIX routes but can also attach them to consumers. We can now move the limit-count plugin. routes:
  - uri: /get
    upstream:
      nodes:
        "httpbin:80": 1
    plugins:
      key-auth: ~                      #1

consumers:
  - username: johndoe
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    plugins:
      key-auth:
        key: jane
      limit-count:
        count: 5                       #2
        time_window: 60
        rejected_code: 429
#END The route is only accessible to requests authenticating with key-auth
johndoe has a lower limit count than janedoe. Did he forget to pay his subscription fees? curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get The second request gets rate-limited. Per-group rate limiting We never attach permissions directly to identities in Identity Management systems. It's considered bad practice because when a person moves around the organization, we need to add and remove permissions one by one. The good practice is to attach permissions to groups and set the person in that group. When the person moves, we change their group; the person loses permissions from the old group and gets permissions from the new group. People get their permissions transitively via their groups. Apache APISIX offers an abstraction called a Consumer Group for this. Let's create two consumer groups with different rate limit values: consumer_groups:
  - id: 1
    plugins:
      limit-count:
        count: 1
        time_window: 60
        rejected_code: 429
  - id: 2
    plugins:
      limit-count:
        count: 5
        time_window: 60
        rejected_code: 429 The next step is to attach consumers to these groups: consumers:
  - username: johndoe
    group_id: 1
    plugins:
      key-auth:
        key: john
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get The second request gets rate-limited. We have the same results as before with two benefits. The first one is as I wrote above: when consumers move in and out, they change their permissions accordingly. The second benefit is that the limit count is shared among all consumers of a group.  Indeed, when you set a limit, you don't want each consumer to be rate limited at X requests per Y second; you want the group as a whole to share the limit. In this way, if a single consumer is very active, they will naturally cap the rate of other consumers who share the same group. Of course, you can set a limit on both a consumer and the group it belongs to. In this case, the lowest limit will apply first. consumers:
  - username: johndoe
    group_id: 2                        #1  
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane Move johndoe to group 2
Limit him individually curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get #1 johndoe hits the limit here, but janedoe now only has four requests left from this minute, as the former used one request Conclusion In this post, we implement rate limiting with Apache APISIX. We set the rate limit on a route and moved it to individual consumers. Then we moved it to consumer groups, so all consumers in a group share the same "pool". The complete source code for this post can be found on GitHub. To go further: Consumer
Consumer Group
Apache APISIX Hands-on Lab In my talk, “Evolving your APIs,” I mention that an API gateway is a Reverse Proxy "on steroids.” One key difference between the former and the latter is that the API Gateway is not unfriendly to business logic. The poster child is rate-limiting. Rate-limiting is an age-old Reverse Proxy feature focused on protecting against Distributed Denial of Service (DDoS) attacks. It treats all clients the same and is purely technical. In this day and age, most API providers offer different subscription tiers; the higher the tier, the higher the rate limit, and the more you pay incidentally. It's not technical anymore and requires to differentiate between clients. In this post, I want to detail how to do it with Apache APISIX. Note I take most of the material from the workshop . workshop Rate-limiting for the masses Apache APISIX offers no less than three plugins to rate limit requests: limit conn: limits the number of concurrent requests limit req: limits the number of requests based on the Leaky Bucket algorithm limit count: limits the number of requests based on a fixed time window limit conn : limits the number of concurrent requests limit conn limit req : limits the number of requests based on the Leaky Bucket algorithm limit req Leaky Bucket limit count : limits the number of requests based on a fixed time window limit count The limit-count plugin is a good candidate for this post. limit-count Let's configure the plugin for a route: routes:
  - uri: /get
    upstream:
      nodes:
        "http://httpbin.org:80": 1
    plugins:
      limit-count:                     #1
        count: 1                       #2
        time_window: 60                #2
        rejected_code: 429             #3
#END routes:
  - uri: /get
    upstream:
      nodes:
        "http://httpbin.org:80": 1
    plugins:
      limit-count:                     #1
        count: 1                       #2
        time_window: 60                #2
        rejected_code: 429             #3
#END Set the limit-count plugin Limit requests to one every 60 seconds Override the default HTTP response code, i.e., 503 Set the limit-count plugin limit-count Limit requests to one every 60 seconds Override the default HTTP response code, i.e. , 503 i.e. 503 At this point, we configured regular rate limiting. curl -v http://localhost:9080/get
curl -v http://localhost:9080/get curl -v http://localhost:9080/get
curl -v http://localhost:9080/get If we execute the second request before a minute has passed, the result is the following: HTTP/1.1 429 Too Many Requests
Date: Tue, 09 Jul 2024 06:55:07 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 241
Connection: keep-alive
X-RateLimit-Limit: 1                   #1
X-RateLimit-Remaining: 0               #2
X-RateLimit-Reset: 59                  #3
Server: APISIX/3.9.1

<html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<hr><center>openresty</center>
<p><em>Powered by <a href="https://apisix.apache.org/">APISIX</a>.</em></p></body>
</html> HTTP/1.1 429 Too Many Requests
Date: Tue, 09 Jul 2024 06:55:07 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 241
Connection: keep-alive
X-RateLimit-Limit: 1                   #1
X-RateLimit-Remaining: 0               #2
X-RateLimit-Reset: 59                  #3
Server: APISIX/3.9.1

<html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<hr><center>openresty</center>
<p><em>Powered by <a href="https://apisix.apache.org/">APISIX</a>.</em></p></body>
</html> Configured limit Remaining quota Waiting time in seconds before quota replenishment Configured limit Remaining quota Waiting time in seconds before quota replenishment Per-consumer rate limiting To configure per-consumer rate limiting, we first need to implement request authentication. APISIX offers many authentication plugins; we shall use the simplest one, key-auth . key-auth checks a specific HTTP request header - apikey by default. key-auth key-auth apikey Here's how we configure consumers: consumers:
  - username: johndoe                  #1
    plugins:
      key-auth:
        key: john                      #2
  - username: janedoe                  #1
    plugins:
      key-auth:
        key: jane                      #2 consumers:
  - username: johndoe                  #1
    plugins:
      key-auth:
        key: john                      #2
  - username: janedoe                  #1
    plugins:
      key-auth:
        key: jane                      #2 Users HTTP header request value Users HTTP header request value curl -H 'apikey: john' localhost:9080/get #1
curl -H 'apikey: jane' localhost:9080/get #2 curl -H 'apikey: john' localhost:9080/get #1
curl -H 'apikey: jane' localhost:9080/get #2 Authenticate as johndoe Authenticate as janedoe Authenticate as johndoe johndoe Authenticate as janedoe janedoe In general, you attach plugins to APISIX routes but can also attach them to consumers. We can now move the limit-count plugin. limit-count routes:
  - uri: /get
    upstream:
      nodes:
        "httpbin:80": 1
    plugins:
      key-auth: ~                      #1

consumers:
  - username: johndoe
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    plugins:
      key-auth:
        key: jane
      limit-count:
        count: 5                       #2
        time_window: 60
        rejected_code: 429
#END routes:
  - uri: /get
    upstream:
      nodes:
        "httpbin:80": 1
    plugins:
      key-auth: ~                      #1

consumers:
  - username: johndoe
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    plugins:
      key-auth:
        key: jane
      limit-count:
        count: 5                       #2
        time_window: 60
        rejected_code: 429
#END The route is only accessible to requests authenticating with key-auth johndoe has a lower limit count than janedoe. Did he forget to pay his subscription fees? The route is only accessible to requests authenticating with key-auth key-auth johndoe has a lower limit count than janedoe . Did he forget to pay his subscription fees? johndoe janedoe curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get The second request gets rate-limited. Per-group rate limiting We never attach permissions directly to identities in Identity Management systems. It's considered bad practice because when a person moves around the organization, we need to add and remove permissions one by one. The good practice is to attach permissions to groups and set the person in that group. When the person moves, we change their group; the person loses permissions from the old group and gets permissions from the new group. People get their permissions transitively via their groups. transitively Apache APISIX offers an abstraction called a Consumer Group for this. Consumer Group Let's create two consumer groups with different rate limit values: consumer_groups:
  - id: 1
    plugins:
      limit-count:
        count: 1
        time_window: 60
        rejected_code: 429
  - id: 2
    plugins:
      limit-count:
        count: 5
        time_window: 60
        rejected_code: 429 consumer_groups:
  - id: 1
    plugins:
      limit-count:
        count: 1
        time_window: 60
        rejected_code: 429
  - id: 2
    plugins:
      limit-count:
        count: 5
        time_window: 60
        rejected_code: 429 The next step is to attach consumers to these groups: consumers:
  - username: johndoe
    group_id: 1
    plugins:
      key-auth:
        key: john
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane consumers:
  - username: johndoe
    group_id: 1
    plugins:
      key-auth:
        key: john
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get
curl -H 'apikey: jane' localhost:9080/get The second request gets rate-limited. We have the same results as before with two benefits. The first one is as I wrote above: when consumers move in and out, they change their permissions accordingly. The second benefit is that the limit count is shared among all consumers of a group.  Indeed, when you set a limit, you don't want each consumer to be rate limited at X requests per Y second; you want the group as a whole to share the limit. In this way, if a single consumer is very active, they will naturally cap the rate of other consumers who share the same group. Of course, you can set a limit on both a consumer and the group it belongs to. In this case, the lowest limit will apply first. consumers:
  - username: johndoe
    group_id: 2                        #1  
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane consumers:
  - username: johndoe
    group_id: 2                        #1  
    plugins:
      key-auth:
        key: john
      limit-count:
        count: 1                       #2
        time_window: 60
        rejected_code: 429
  - username: janedoe
    group_id: 2
    plugins:
      key-auth:
        key: jane Move johndoe to group 2 Limit him individually Move johndoe to group 2 johndoe Limit him individually curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get #1 curl -H 'apikey: john' localhost:9080/get
curl -H 'apikey: john' localhost:9080/get #1 johndoe hits the limit here, but janedoe now only has four requests left from this minute, as the former used one request johndoe hits the limit here, but janedoe now only has four requests left from this minute, as the former used one request johndoe janedoe Conclusion In this post, we implement rate limiting with Apache APISIX. We set the rate limit on a route and moved it to individual consumers. Then we moved it to consumer groups, so all consumers in a group share the same "pool". The complete source code for this post can be found on GitHub . GitHub To go further: To go further: Consumer Consumer Group Apache APISIX Hands-on Lab Consumer Consumer Consumer Group Consumer Group Apache APISIX Hands-on Lab Apache APISIX Hands-on Lab

Advanced Rate Limiting with Apache APISIX: Optimizing API Gateway Performance

GATEWAY

mygateway.xyz

-- employees

Since n.d.

COMPANY RANKING

GATEWAY

EVERGREEN INDEX #641

Representing this company? Click here to claim and customize this page!

Gateway WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

GATEWAY

mygateway.xyz

-- employees

Since n.d.

COMPANY RANKING

GATEWAY

EVERGREEN INDEX #641

RELATED COMPANIESRANK

STORIES ABOUT GATEWAY

Representing this company? Click here to claim and customize this page!

Gateway WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!