# Gcore Docs - Full Index > Complete article index across all Gcore products. 576 articles. > Use this file for offline indexing, bulk vectorization, or large-context retrieval. # Gcore Account settings > Configure Gcore Customer Portal account settings including user profile, two-factor authentication, billing, payments, user roles and permissions, API tokens, notifications, and support access. - [Account settings](https://gcore.com/docs/account-settings.md): Configure Gcore Customer Portal account settings including user profile, two-factor authentication, billing, payments, user roles and permissions, API tokens, notifications, and support access. ## My profile - [My profile settings](https://gcore.com/docs/account-settings/my-profile/overview.md): Configure personal user account settings including username, email, preferred language, two-factor authentication (2FA), password changes, and view login history with IP address, OS, browser, and success status tracking in the Customer Portal My profile page. - [Set up two-factor authentication](https://gcore.com/docs/account-settings/my-profile/two-factor-authentication.md): Enable two-factor authentication in Gcore Customer Portal using authenticator applications (Google Authenticator, Microsoft Authenticator, Authy) with QR code scanning and backup verification codes for account security. - [Change or reset a password](https://gcore.com/docs/account-settings/my-profile/change-password.md): Change or reset account password in Gcore Customer Portal via Profile settings, or reset forgotten password via email verification link at auth.gcore.com/login/forgot-password. - [Missing password reset email](https://gcore.com/docs/account-settings/my-profile/password-reset-email.md): Troubleshoot missing password reset emails from support@gcore.com by checking spam folders and reinitiating the reset process at auth.gcore.com/login/forgot-password. ## Account - [Account settings](https://gcore.com/docs/account-settings/account/overview.md): Configure account identification, billing address, tax location, and currency settings in Gcore Customer Portal; switch individual accounts to company status via KYC verification and business documentation submission. - [Create an account for an individual or legal entity](https://gcore.com/docs/account-settings/account/create-account.md): Create a Gcore account for individuals using Google, GitHub, or email authentication, or contact sales for legal entity contract negotiation before accessing the Customer Portal and billing configuration. - [Create an additional account and switch between accounts](https://gcore.com/docs/account-settings/account/additional-accounts.md): Create additional accounts and switch between multiple accounts from a single login using the profile menu and account switcher without re-authorization. - [Disable or resume services](https://gcore.com/docs/account-settings/account/services.md): Disable or resume Gcore services via Customer Portal Services page, managing Active and Stopped service statuses with automatic suspension and data deletion after specified periods. - [Account deletion](https://gcore.com/docs/account-settings/account/account-deletion.md): Request permanent account deletion via Settings > Account > General information > Delete account; account enters Suspended state, all services stop immediately, and deletion is blocked if account has outstanding debt balance. ## Billing - [Billing overview](https://gcore.com/docs/account-settings/billing/overview.md): Manage consumption-based billing with monthly data collection on the 2nd day and 5-minute intervals for Cloud Pay-As-You-Go tariffs with threshold billing at 4 €/$ limits. - [Expenses](https://gcore.com/docs/account-settings/billing/expenses.md): View consumed Gcore product costs by date, service, feature, usage, and pricing rule status (commitment or overcommitment) on the Expenses page; inspect tax rates, discount percentages, and tax amounts in expense breakdowns. - [Payments and payment methods](https://gcore.com/docs/account-settings/billing/payments.md): View payment history, transaction details (ID, date, payment method, sum, status), and filter payments by method, date, or status in Billing > Payments; add or update payment methods (Debit or credit card, PayPal, bank, Apple Pay, Google Pay, Alipay) in Account > Payment methods with automatic verification charge and refund processing. - [Bonuses and discounts](https://gcore.com/docs/account-settings/billing/bonuses-and-discounts.md): View bonus credits and active discounts in the Gcore portal Billing section, including bonus credit status (Credited, Charged, Expired), expiration dates, applicability by product category (Cloud, CDN), discount percentage, service, feature, valid date range, and associated promo codes. - [Trial conditions](https://gcore.com/docs/account-settings/billing/trial-conditions.md): Activate free trials for Gcore services including CDN (14 days or 300 GB), Video Streaming (14 days and 10 minutes), Web Application Security (3 days), and Managed DNS Pro (14 days) via the personal account dashboard or Services billing page. - [VAT rates in different countries for an individual and legal entity](https://gcore.com/docs/account-settings/billing/vat-rates.md): Determine VAT rates for individuals and organizations by country and registration type, with rates varying by EU member state (0-27% for organizations with VAT number, 16-27% without) and user classification (individual or legal entity). - [TAX location](https://gcore.com/docs/account-settings/billing/tax-location.md): Configure tax location in billing profile based on address, payment method, and IP address to apply correct VAT rates and tax regulations; update VAT number and tax jurisdiction via billing profile or support contact. - [Data deletion](https://gcore.com/docs/account-settings/billing/data-deletion.md): Manage data deletion timelines for suspended Gcore products including CDN, Edge Cloud (Managed Kubernetes, Function as a Service, Container as a Service, Managed PostgreSQL), Object Storage, Managed DNS, Video Streaming, Web Application Security, DDoS Protection, and WAAP, with retention periods ranging from immediate deletion to 90 days depending on product type. ## Users - [About users](https://gcore.com/docs/account-settings/users/about-users.md): Manage user roles and permissions in Gcore Customer Portal - Administrators, Engineers, and Purge/Prefetch roles with rights to manage CDN, Video Streaming, Managed DNS, Object Storage, and WAAP services; assign roles, invite users, create API tokens, and enable 2-Factor authentication. - [Invite, edit, and delete a user](https://gcore.com/docs/account-settings/users/manage-users.md): Invite users to Gcore Customer Portal with email, name, interface language, and role assignments across CDN, IAM, Edge Cloud, Billing, Managed DNS, Object Storage, Video Streaming, and Web Application Security services. - [Create, use, or delete a permanent API token](https://gcore.com/docs/account-settings/api-tokens.md): Create, use, or delete permanent API tokens with configurable expiration dates, role-based access control, and APIKey authorization header for automated API requests to Gcore services. - [Manage service notifications and promotional emails](https://gcore.com/docs/account-settings/notifications.md): Configure product notifications, technical notifications, and promotional emails per user in Gcore Customer Portal via the Notifications page, with shared general notification settings across all account users and CDN traffic consumption level alerts checked hourly. - [How quickly our support team will respond to you](https://gcore.com/docs/account-settings/how-quickly-our-support-team-will-respond-to-you.md): Configure support response times based on billing plan (free, medium 8/5, PRO+ 24/7), request priority levels (P1–P4), and support team workload across CDN, Video Streaming, Edge Cloud, Web Application Protection, Object Storage, and Managed DNS services. - [Be aware of the service status, scheduled and emergency maintenance](https://gcore.com/docs/account-settings/be-aware-of-the-service-status-scheduled-and-emergency-maintenance.md): Subscribe to Gcore Status Page via email, Slack, or webhook to receive notifications about service incidents, scheduled maintenance, and outages; configure component-specific alerts and manage Slack workspace integrations. - [Roadmap: Provide feedback, suggest new features, follow development](https://gcore.com/docs/account-settings/roadmap-provide-feedback-suggest-new-features-follow-development.md): Submit feature requests and track development status for CDN, Managed DNS, Edge Cloud, Video Streaming, and Web Application Security products via Gcore Roadmap, with posts organized in In Review, Planned, In Progress, and Completed columns. --- # Gcore Developer Tools > REST API, SDKs, MCP Server, Terraform. ## REST API - [Gcore REST API](https://gcore.com/docs/developer-tools/rest-api/overview.md): Entry point for the Gcore REST API covering authentication, base URLs for all products including Cloud, CDN, DNS and Storage, and a learning path from first call through pagination and SDK usage. - [API basics](https://gcore.com/docs/developer-tools/rest-api/api-basics.md): Foundational concepts for calling the Gcore API from a terminal, including how to install and use curl, how to read JSON responses, how to store the API token as an environment variable, and what HTTP status codes mean. - [Authenticate to the Gcore API](https://gcore.com/docs/developer-tools/rest-api/authentication.md): Create a permanent API token in the Gcore Customer Portal, store it as an environment variable, verify the token, and understand token roles, expiry limits, and SSO account behavior. - [Make the first Gcore API call](https://gcore.com/docs/developer-tools/rest-api/first-api-call.md): Step-by-step walkthrough to obtain a project ID and region ID from the Cloud API, set all three required variables in the terminal, and make a verified first resource call using curl, Python SDK, Go SDK, or JavaScript. - [Asynchronous operations and task polling](https://gcore.com/docs/developer-tools/rest-api/async-operations.md): Gcore Cloud API write operations return a task ID while the operation runs in the background; explains how to poll the task endpoint for completion, read the created resource ID from the response, and handle errors and timeouts. - [Error handling](https://gcore.com/docs/developer-tools/rest-api/error-handling.md): Gcore API error responses contain a machine-readable error type, a human-readable message, and a request ID; covers ValidationError, NotFoundError, QuotaLimitExceed, ForbiddenError, HTTP status codes, and retry strategy. - [Pagination](https://gcore.com/docs/developer-tools/rest-api/pagination.md): Gcore API list endpoints return paginated results using limit and offset query parameters; explains the count and results response structure and shows how to iterate through all pages in curl, Python SDK, Go SDK, and JavaScript. - [API tools](https://gcore.com/docs/developer-tools/rest-api/tools.md): Setup guides for Postman with OpenAPI spec import, HTTPie as a readable curl alternative, VS Code REST Client with dot-http files and dotenv token storage, and Bruno or Insomnia as open-source GUI alternatives. ## SDKs - [Gcore API SDKs](https://gcore.com/docs/developer-tools/sdks/overview.md): Overview of official Gcore API SDKs for Python and Go, JavaScript fetch and axios examples, and a guide for choosing the right client for scripting, automation, or production services. - [Python SDK](https://gcore.com/docs/developer-tools/sdks/python.md): Official Gcore Python SDK for REST API access - installation, client initialization with project and region defaults, method naming patterns, task polling with create-and-poll, automatic pagination, error handling with typed exceptions, retries, timeouts, and async usage with AsyncGcore and aiohttp. - [Go SDK](https://gcore.com/docs/developer-tools/sdks/go.md): Official Gcore Go SDK for REST API access - installation, client initialization, param.Opt and omitzero request field semantics, auto-paging list iterators, error handling with errors.As, retries, per-request and per-retry timeouts, middleware, and accessing raw HTTP response data. ## MCP Server - [Gcore MCP Server overview](https://gcore.com/docs/developer-tools/mcp-server/gcore-mcp-server-overview.md): Deploy Gcore MCP Server to expose CDN, Cloud, DNS, FastEdge, IAM, Security, Storage, Streaming, and WAAP API operations as callable tools for AI assistants via Model Context Protocol, supporting Claude Code, Cursor IDE, and MCP Inspector clients with automatic tool schema loading and multi-step workflow chaining. - [Install and configure Gcore MCP Server](https://gcore.com/docs/developer-tools/mcp-server/install-and-configure-gcore-mcp-server.md): Install Gcore MCP Server using uv package manager, create an API token with product-specific permissions, configure GCORE_API_TOKEN and optional GCORE_PROJECT_ID and GCORE_REGION_ID environment variables, and verify server connectivity via uvx or global installation for Claude Code and Cursor IDE integration. - [Connect Cursor IDE to Gcore MCP Server](https://gcore.com/docs/developer-tools/mcp-server/connect-cursor-to-gcore-mcp-server.md): Configure Cursor IDE 0.40+ to connect Gcore MCP Server with product-specific tool patterns (dns.*, storage.*, cdn.*) under 50-tool limit using Gcore API token in MCP configuration file. - [Connect Claude Code to Gcore MCP Server](https://gcore.com/docs/developer-tools/mcp-server/connect-claude-code-to-gcore-mcp-server.md): Configure Gcore MCP Server in Claude Code by installing uv package manager, authenticating with a Claude Pro/Max/Team/Enterprise account, adding Gcore API token to the MCP configuration file, and verifying connection status with resource queries to enable deferred schema loading for Gcore API operations. - [Available products and tools](https://gcore.com/docs/developer-tools/mcp-server/gcore-mcp-server-available-products-and-tools.md): Access Gcore MCP Server tools organized by product - CDN (85 tools), Cloud compute/storage/networking (350 tools), DNS (35 tools), FastEdge (20 tools), IAM (20 tools), and Storage (40 tools) with resource-specific operations like list, create, update, delete, and product-specific actions via filter patterns. - [Filter tools with GCORE_TOOLS](https://gcore.com/docs/developer-tools/mcp-server/filter-tools-with-gcore-tools.md): Configure GCORE_TOOLS environment variable to filter MCP Server tool exposure using predefined toolsets (account, instances, baremetal, gpu_clusters, networks, security, storage, billing, registries, inference), wildcard patterns (cdn_*, cloud_*), and exact tool names separated by commas to reduce context consumption and improve model tool selection accuracy. - [Explore and debug tools with MCP Inspector](https://gcore.com/docs/developer-tools/mcp-server/test-tools-with-mcp-inspector.md): Configure MCP Inspector to connect to Gcore MCP Server via stdio or HTTP transport, explore available tools filtered by product type (DNS, CDN, Cloud), and manually execute tools with parameters to test behavior before integration with Claude Code. ## Terraform - [Overview](https://gcore.com/docs/developer-tools/terraform/overview.md): Install the Gcore Terraform provider, configure v0 and v2 authentication, and manage Cloud and CDN resources via infrastructure-as-code. - [Get started with Terraform](https://gcore.com/docs/developer-tools/terraform/get-started-with-terraform.md) - [Manage a Terraform project](https://gcore.com/docs/developer-tools/terraform/use-variables-and-organize-a-terraform-project.md) - [Import existing Gcore infrastructure into Terraform](https://gcore.com/docs/developer-tools/terraform/import-existing-gcore-infrastructure-into-terraform.md) - [Migrate from Gcore Terraform provider v0 to v2](https://gcore.com/docs/developer-tools/terraform/migrate-v0-to-v2.md) - [Copy resources across environments](https://gcore.com/docs/developer-tools/terraform/copy-resources-across-environments.md): Replicate Gcore infrastructure across preproduction and production environments using Terraform variables, tfvars files, and workspaces. Applies to CDN, Cloud, and DNS resources with both provider v0 and v2. --- # Gcore CDN > Configure Gcore CDN resources for content delivery including origin groups, caching rules, SSL certificates, HTTP headers, cache purge, logs, Grafana dashboards, and Terraform integration. - [CDN](https://gcore.com/docs/cdn.md): Configure Gcore CDN resources for content delivery including origin groups, caching rules, SSL certificates, HTTP headers, cache purge, logs, Grafana dashboards, and Terraform integration. ## Getting Started ## Create a CDN resource - [CDN resource overview](https://gcore.com/docs/cdn/getting-started/create-a-cdn-resource/overview.md): Create CDN resources for entire site acceleration, static asset delivery (images, CSS, JavaScript, fonts), or video streaming (HLS, DASH, FLV) with integrated or manual DNS management and up to thirty resources per account. - [Create a CDN resource](https://gcore.com/docs/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource.md): Create a CDN resource by entering a domain name, choosing a DNS option (CNAME-based or Gcore Managed DNS delegation), optionally enabling WAAP for Layer 7 DDoS and web application protection, and configuring an origin or origin group. - [Create a CDN resource for video streaming](https://gcore.com/docs/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource-for-video-streaming.md): Create a CDN resource for video streaming with HLS, DASH, FLV, or MP4 formats, configuring geo-blocking, secure token authentication, custom domains, and origin shielding for global delivery without transcoding. ## Integrate CDN with CMS and other platforms - [About Gcore CDN integration with CMS and other platforms](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms.md): Integrate Gcore CDN with CMS platforms and cloud storage by replacing application domain with custom CDN domain using plugins for WordPress, Drupal, Joomla, Magento, PrestaShop, AWS S3, Google Cloud Storage, Cloudflare, and other supported platforms. - [Integrate CDN resource with AWS S3](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-aws-s3.md): Configure Gcore CDN resource with AWS S3 bucket as origin by creating S3 bucket, enabling Static Website Hosting, setting bucket policy, and using S3 Endpoint URL as CDN origin source with CNAME record. - [Integrate CDN resource with B2evolution](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-b2evolution.md): Configure B2evolution CMS to serve static resources through Gcore CDN by replacing base URL variables with CNAME domain in configuration file, then verify resource URLs are rewritten to CDN CNAME in browser Network tab. - [Integrate CDN resource with Cloudflare](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-clouldflare.md): Configure Gcore CDN integration with Cloudflare by disabling DNS proxying on CNAME records and setting Origin Pull Protocol to HTTP or adding Change SNI Hostname in Security settings to avoid 502 errors. - [Integrate CDN resource with Concrete5](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-concrete5.md): Configure Gcore CDN resource integration with Concrete5 CMS by installing CDN extensions (CDN Manager, Content Delivery Network, or concrete5 CDN package) and entering the CNAME custom domain in extension settings to rewrite static file URLs. - [Integrate CDN resource with Craft](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-craft.md): Configure Gcore CDN resource integration with Craft CMS by creating a new asset source with CDN CNAME, uploading static files, and replacing asset URLs to enable content delivery through the CDN endpoint. - [Integrate CDN resource with Cs-cart](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-cs-cart.md): Install the Gcore CDN Universal Add-on plugin for Cs-cart, configure the CDN URL field with a CNAME record from Gcore Customer Portal, and enable the plugin to rewrite static file URLs through the CDN resource. - [Integrate CDN resource with Django CMS](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-django-cms.md): Configure Django CMS static and media file delivery through Gcore CDN by creating a CDN resource, updating urls.py and settings.py to point to CDN CNAME, and running collectstatic to serve static assets via CDN. - [Integrate CDN resource with Drupal](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-drupal.md): Enable Gcore CDN integration with Drupal by installing the CDN Module, configuring Origin Pull mode with CNAME from Gcore Customer Portal, setting Far Future expiration, and enabling HTTPS for SSL support. - [Integrate CDN resource with Google Cloud Storage](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-google-cloud-storage.md): Configure Gcore CDN resource with Google Cloud Storage bucket as origin, create CNAME record for custom domain, and optionally use Rewrite option to hide bucket name. - [Integrate CDN resource with IPB](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ipb.md): Configure Gcore CDN CNAME integration with Invision Power Board by entering custom domain in System settings General configuration to rewrite image, CSS, and JavaScript URLs. - [Integrate CDN resource with IPS](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ips.md): Configure Gcore CDN CNAME integration with IPS Community by entering the custom domain in System Settings General Configuration CDN Settings and verifying URL rewriting in browser developer tools. - [Integrate CDN resource with Joomla](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-joomla.md): Install the CDN for Joomla plugin from NoNumber.nl via Extensions Manager, configure the CNAME record from Gcore Customer Portal in plugin settings, and verify static file URLs are rewritten to the CDN CNAME domain. - [Integrate CDN resource with Kirby](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-kirby.md): Configure CDN CNAME URLs for Kirby CMS static assets by manually updating CSS and JS file paths in header.php and using the Kirby GetImages plugin for image delivery, then verify rewritten URLs in browser Network tab. - [Integrate CDN resource with Magento](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-magento.md): Configure Gcore CDN integration with Magento by enabling Merge JavaScript Files and Merge CSS Files in Developer settings, then set the CDN CNAME in Web > Unsecure or Secure > Base URL and Base Skin URL configuration sections. - [Integrate CDN resource with Perch](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-perch.md): Configure Perch CMS to deliver static content through Gcore CDN by updating configuration files with CDN resource CNAME and bucket paths, then verify URL rewriting in browser developer tools. - [Integrate CDN resource with PrestaShop](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-prestashop.md): Configure Gcore CDN integration with PrestaShop by enabling CCC (Combine, Compress and Cache) settings in Advanced Parameters/Performance and entering the CDN CNAME in the Media Server field to rewrite static asset URLs. - [Integrate CDN resource with PyroCMS](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-pyrocms.md): Configure Gcore CDN CNAME integration in PyroCMS admin panel via Settings > Integration to rewrite static asset URLs to custom domain. - [Integrate CDN resource with SocialEngine](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-socialengine.md): Integrate CDN resource with SocialEngine by entering CNAME from Gcore Customer Portal in Settings/General Settings, ensuring CNAME record is properly configured, and verifying static file URLs are rewritten to the CDN CNAME domain. - [Integrate CDN resource with Typo3](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-typo3.md): Configure Gcore CDN integration with Typo3 using the smile_cdn extension by installing the plugin, defining the CDN CNAME record, setting asset filters, and flushing frontend caches to rewrite static resource URLs. - [Integrate CDN resource with vBulletin](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-vbulletin.md): Configure CDN resource integration with vBulletin by creating replacement variables in Styles > Replacement Variable Manager to rewrite static file URLs from origin to Gcore CDN CNAME domain. - [Integrate CDN resource with Webasyst](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-webasyst.md): Configure Gcore CDN CNAME integration in Webasyst by entering the custom domain in Site Settings and verifying URL rewriting in browser Developer Tools. ## Wordpress - [Integrate CDN resource with WordPress (Gcore plugin)](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-gcore-plugin.md): Install and configure the Gcore CDN WordPress plugin to enable CDN delivery by setting Enable CDN checkbox, Personal domain, file types (basic or advanced mode with custom extensions), folder paths, and exception URLs. - [Integrate CDN resource with WordPress (Rocket plugin)](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-rocket-plugin.md): Configure Gcore CDN resource integration with WordPress using WP Rocket plugin by entering CNAME from Control Panel, updating Replace Site's Hostname field, and verifying static file URLs are rewritten to CDN CNAME domain. - [Integrate CDN resource with WordPress (W3 Total Cache plugin)](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-w3-total-cache-plugin.md): Configure Gcore CDN integration with WordPress using W3 Total Cache plugin by enabling Generic Mirror CDN type and entering your CDN CNAME in the hostname replacement field. - [Integrate CDN resource with WordPress (WP SuperCache plugin)](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-wp-supercache-plugin.md): Configure WP Super Cache plugin CDN integration by enabling CDN Support, entering Gcore CDN CNAME in Off-site URL field, and verifying static asset URLs are rewritten to the custom domain. - [Integrate CDN resource with X-Cart](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-x-cart.md): Configure Gcore CDN resource integration with X-Cart 4.4.x by setting CNAME record in Customer Portal and modifying smarty.php, func.files.php, function.get_category_image_url.php, and banner_rotator.tpl files to rewrite static asset URLs to CDN CNAME domain. - [Integrate CDN resource with XenForo](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-xenforo.md): Configure Gcore CDN resource integration with XenForo by editing config.php, updating Style General Settings with CDN CNAME domain, and verifying static file URLs are rewritten to the configured CNAME record. - [Extend CDN functionality with FastEdge](https://gcore.com/docs/cdn/getting-started/integrate-cdn-with-fastedge.md): Deploy FastEdge serverless compute functions at CDN edge locations to extend content delivery with custom request/response processing, origin shielding, and dynamic content generation. ## Configure an origin - [Add CDN servers to the origin ACL whitelist](https://gcore.com/docs/cdn/getting-started/configure-an-origin/add-cdn-servers-to-the-origin-acl-whitelist.md): Configure origin ACL whitelist for CDN servers using HTTP headers, IP addresses, or subnets via API endpoints; HTTP header method recommended to avoid manual updates as CDN server IPs change every 30-60 minutes. - [Сonfigure HTTP/2 on the origin](https://gcore.com/docs/cdn/getting-started/configure-an-origin/configure-http-2-on-the-origin.md): Enable HTTP/2 protocol on CDN origin servers by configuring Nginx 1.9.5+ with listen directive or Apache 2.4.17+ with mod_http2 module to support multiplexed content delivery over single TCP connections. - [CDN timeouts](https://gcore.com/docs/cdn/getting-started/cdn-timeouts.md): Configure Gcore CDN Edge Network proxy timeouts including proxy_read_timeout (30s), proxy_connect_timeout (5s), proxy_send_timeout (30s), and client_header_timeout for origin server connections and client request handling. - [About CDN resources interface: how it is arranged](https://gcore.com/docs/cdn/about-cdn-resources-interface-how-it-is-arranged.md): Create and manage CDN resources in the Gcore Customer Portal with filtering by status (Active, Suspended, Processing, Deleted), search by CNAME or resource ID, and per-resource operations including Settings, Statistics, Suspend resource, LIVE STREAMING preset, and Delete resource. Purge and Prefetch are accessible from the CDN navigation menu. - [Add an origin group to a CDN resource](https://gcore.com/docs/cdn/add-an-origin-group.md): Create and attach origin groups to CDN resources with single or multiple origins, configuring round-robin load balancing between active origins and backup failover logic for 5xx errors. ## CDN resource options ## General - [Specify an origin and the origin pull protocol](https://gcore.com/docs/cdn/cdn-resource-options/general/specify-an-origin-and-the-origin-pull-protocol.md): Configure CDN origin pull protocol (HTTP, HTTPS, or HTTP and HTTPS) and specify origin server IP address or domain for content delivery, controlling which protocol CDN servers use to fetch content from the origin and how client requests are routed based on protocol matching. - [Use a private bucket as an origin](https://gcore.com/docs/cdn/cdn-resource-options/general/use-a-private-bucket-as-an-origin.md): Configure private S3-compatible buckets as CDN origins using AWS Signature V4 authentication with Access Key ID, Secret Access Key, Hostname, and Region parameters for Amazon or Gcore Object Storage. - [Enable origin SSL validation](https://gcore.com/docs/cdn/cdn-resource-options/general/enable-origin-ssl-validation.md): Enable origin SSL validation for CDN resources by uploading X.509 certificates in PEM format via the Add Trusted CA Certificate API endpoint, then linking certificates to CDN resources using proxy_ssl_ca, proxy_ssl_data, and proxy_ssl_enabled parameters to verify origin server identity and prevent Man-in-the-Middle attacks. - [Create and set a custom domain for the content delivery via CDN](https://gcore.com/docs/cdn/cdn-resource-options/general/create-and-set-a-custom-domain-for-the-content-delivery-via-cdn.md): Create custom domains and additional domains for CDN static content delivery by specifying domain names in the CDN resource configuration and adding CNAME records pointing to the account-specific gcdn.co endpoint. - [Enable and configure origin shielding](https://gcore.com/docs/cdn/cdn-resource-options/general/enable-and-configure-origin-shielding.md): Enable origin shielding in Gcore CDN by toggling the feature in Resource settings and selecting a precache server location to reduce origin server load from multiple CDN edge servers. - [Suspend a CDN resource automatically or manually](https://gcore.com/docs/cdn/cdn-resource-options/general/suspend-a-cdn-resource-automatically-or-manually.md): Suspend CDN resources automatically after 90 days of inactivity or manually via Content availability toggle in resource settings; automatic suspension triggers email notifications to administrator and engineer roles 7 days before suspension. - [Customize connection and read timeouts](https://gcore.com/docs/cdn/cdn-resource-options/general/customize-connection-and-read-timeouts.md): Configure custom connection timeout and read timeout for CDN resources to specify how long edge nodes wait when connecting to origin servers and receiving responses before returning 504 Gateway Timeout errors. ## Cache - [Specify cache lifetime on a CDN resource or origin](https://gcore.com/docs/cdn/cdn-resource-options/cache/specify-cache-lifetime-on-a-cdn-resource-or-origin.md): Configure CDN cache lifetime using Origin controlled or CDN controlled modes with Cache-Control headers (max-age parameter) in Apache .htaccess or Nginx nginx.conf, or set Default cache expiry in the CDN control panel to control how long files are stored in CDN servers before revalidation via ETag comparison. - [Set up a CDN resource to follow origin redirects](https://gcore.com/docs/cdn/cdn-resource-options/cache/set-up-a-cdn-resource-to-follow-origin-redirects.md): Enable CDN origin redirection to follow HTTP 3xx status codes (301, 302, 303, 307, 308) returned by the origin server, with automatic content retrieval and caching via Gcore Customer Portal or API using the enabled and codes properties. - [Specify cache lifetime for user browsers](https://gcore.com/docs/cdn/cdn-resource-options/cache/specify-cache-lifetime-for-user-browsers.md): Configure browser cache lifetime using Origin controlled mode with Cache-Control headers or CDN controlled mode with custom max-age values in seconds, controlling Cache-Control, Expires, and X-Cached-Since response headers for HTTP status codes 200, 201, 204, 206, 301, 302, 303, 304, 307, 308. - [Ignore the set cookie or query string parameters when caching content on CDN servers](https://gcore.com/docs/cdn/cdn-resource-options/cache/ignore-the-set-cookie-or-query-string-parameters-when-caching-content-on-cdn-servers.md): Configure CDN query string caching behavior using Ignore All, Ignore All Except, or Ignore Only modes to control cache key generation for URLs with query parameters. - [Always online: provide the stale cache if the origin is unavailable](https://gcore.com/docs/cdn/cdn-resource-options/cache/always-online-provide-the-stale-cache-if-the-origin-is-unavailable.md): Configure Always Online to serve stale cached content when origin is unavailable due to network errors, timeouts, invalid headers, or HTTP 5xx/4xx errors, with X-Cache - Stale response header and automatic origin availability checks per request. - [Сache Sharding: share cache between CDN servers](https://gcore.com/docs/cdn/cdn-resource-options/cache/cache-sharding-share-cache-between-cdn-servers.md): Enable Cache Sharding on CDN resources to share cache between servers in the same Point of Presence using consistent hashing algorithm, improving cache hit rates for content-heavy applications like e-commerce, video streaming, and VoD platforms. - [Modify cache key](https://gcore.com/docs/cdn/cdn-resource-options/cache/modify-cache-key.md): Configure cache key variables (URI, protocol, normalized URI) in Gcore CDN resources via portal or API to control cache object identification and improve cache hit ratio. ## Access - [Control access to the content with country, referrer, IP, and user agents policies](https://gcore.com/docs/cdn/cdn-resource-options/security/control-access-to-the-content-with-country-referrer-ip-and-user-agents-policies.md): Configure CDN resource access policies by country, referrer domain, and IP address ranges using allow or block rules in Resource settings via portal or API. - [Set up a redirect from HTTP to HTTPS](https://gcore.com/docs/cdn/cdn-resource-options/security/set-up-a-redirect-from-http-to-https.md): Configure HTTP to HTTPS redirect on CDN resources via Gcore Customer Portal Access section or API, requiring an active SSL certificate in the General section first. ## Secure token - [About secure token](https://gcore.com/docs/cdn/cdn-resource-options/security/use-a-secure-token/about-secure-token.md): Configure Gcore CDN Secure Token to protect content with time-based expiration and IP address restrictions, returning 410 Gone responses for expired tokens and unauthorized IP requests. - [Configure and use secure token](https://gcore.com/docs/cdn/cdn-resource-options/security/use-a-secure-token/configure-and-use-secure-token.md): Configure secure token in Gcore CDN resources by enabling the option, setting a 6-32 character key, optionally binding to client IP, and generating MD5-hashed secure links with Unix timestamp expiration using PHP, Python, or OpenSSL scripts; validate token hash, expiration timestamp, and file or directory path on each request. - [Specify HTTP methods allowed for content requests from the CDN](https://gcore.com/docs/cdn/cdn-resource-options/security/specify-http-methods-allowed-for-content-requests-from-the-cdn.md): Configure allowed HTTP methods (GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS) for CDN resources via the Enable HTTP methods toggle to block unauthorized requests and return 405 Method Not Allowed responses. - [Set the hostname passed in SNI requests to the origin](https://gcore.com/docs/cdn/cdn-resource-options/security/set-the-hostname-passed-in-sni-requests-to-the-origin-server.md): Configure SNI hostname in CDN HTTPS origin requests using Dynamic mode matching Host Header or Custom mode with a specified hostname value. - [Specify TLS versions allowed for content requests from the CDN](https://gcore.com/docs/cdn/cdn-resource-options/security/choose-tls-versions.md): Configure allowed TLS protocol versions (SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3) for CDN content requests via the Gcore Customer Portal to block unspecified versions. ## Security - [Protect CDN resources with Gcore WAAP](https://gcore.com/docs/cdn/cdn-resource-options/cdn-security/protect-cdn-resources-with-basic-waf.md): Enable WAAP (Web Application and API Protection) for CDN resources via the Customer Portal Security section to activate Layer 7 DDoS protection, web app security, and API protection; create CDN rules with WAAP exceptions to prevent blocking legitimate content by matching URLs or regex patterns. ## Compression - [Configure Gzip and Brotli compression](https://gcore.com/docs/cdn/cdn-resource-options/compression/configure-gzip-and-brotli-compression.md): Enable Gzip and Brotli edge compression in Gcore CDN to compress content at edge nodes before serving to browsers, supporting MIME types including text/html, application/javascript, application/json, image/svg+xml, and application/wasm with configurable compression methods based on Accept-Encoding headers. - [Configure fetch compression](https://gcore.com/docs/cdn/cdn-resource-options/compression/configure-fetch-compression.md): Enable Fetch compressed in CDN resource Content settings to pull already-compressed content from origin servers supporting GZip compression, reducing bandwidth and delivery time between origin and CDN edge servers. - [Configuring HTTP status codes for CDN-hosted content](https://gcore.com/docs/cdn/cdn-resource-options/specify-custom-http-status-code-for-the-content-delivered-by-the-cdn.md): Configure custom HTTP status codes for Gcore CDN resources globally via Resource settings or selectively via Rules, with optional redirect URLs, status text, and time-based scheduling by timezone. - [Optimize large file delivery](https://gcore.com/docs/cdn/cdn-resource-options/optimize-large-file-delivery.md): Enable Large File Delivery Optimization in Gcore CDN to serve files larger than 10 MB using HTTP Range requests with 10 MB chunks, requiring origin support for Range Requests, consistent Content-Length and Etag headers, and incompatibility with Fetch Compressed, Gzip Compression, and Brotli Compression options. - [Rewrite: redirect requests from the CDN to the origin](https://gcore.com/docs/cdn/cdn-resource-options/rewrite-redirect-requests-from-the-cdn-to-the-origin.md): Configure CDN Rewrite option with nginx-compatible regular expressions to redirect request paths from CDN to origin, using space-separated directives with capture groups ($1, $2) and optional flags like break, last, redirect, permanent. - [WebSockets: allow permanent connections with the origin](https://gcore.com/docs/cdn/cdn-resource-options/websockets-allow-permanent-connections-with-the-origin.md): Enable or disable WebSocket protocol support on CDN resources to allow persistent bidirectional TCP connections between clients and origin servers for real-time data exchange. ## HTTP headers - [Specify HTTP headers that CDN adds to requests to the origin](https://gcore.com/docs/cdn/cdn-resource-options/http-headers/specify-http-headers-that-cdn-adds-to-requests-to-the-origin.md): Configure HTTP request headers that Gcore CDN adds to origin requests via the Request Headers option, specifying header names and values with supported characters (letters, numbers, dashes, underscores, slashes, colons, equals, dots, spaces). - [Add the Access-Control-Allow-Origin header to the browser response](https://gcore.com/docs/cdn/cdn-resource-options/http-headers/add-the-access-control-allow-origin-header-to-the-browser-response.md): Configure Access-Control-Allow-Origin CORS headers in Gcore CDN resources via resource settings, rule creation, or origin server to allow cross-origin requests from specific domains or all origins using wildcard or domain whitelist options. - [Add or hide response headers](https://gcore.com/docs/cdn/cdn-resource-options/http-headers/add-or-hide-response-headers.md): Configure custom HTTP response headers in Gcore CDN via the "Response headers (add)" option to add up to 50 headers with custom names and values to CDN server responses, supporting multiple values per header separated by commas or line breaks and filtering by HTTP status codes. - [Configure and check the host header](https://gcore.com/docs/cdn/cdn-resource-options/http-headers/configure-and-check-the-host-header.md): Configure the Host header in Gcore CDN resources using Custom Host header or Forward Host header options in HTTP headers settings to specify origin domain/IP address, and verify header values with curl or diagnostic tools to prevent 4xx/5xx errors. - [Use the X-Forwarded-Proto header to identify the protocol used for CDN servers requests](https://gcore.com/docs/cdn/cdn-resource-options/http-headers/use-the-x-forwarded-proto-header-to-identify-the-protocol-used-for-cdn-servers-requests.md): Configure X-Forwarded-Proto header in CDN to identify client protocol (HTTP or HTTPS) for implementing HTTP-to-HTTPS redirects and protocol-based content delivery. - [Network limits: set the content delivery speed to end users](https://gcore.com/docs/cdn/cdn-resource-options/network-limits-set-the-content-delivery-speed-to-end-users.md): Configure CDN Download Speed Limit in Static or Dynamic mode to control content delivery speed per connection in KB/s, with parameters for Connection Speed, Limit After, speed query argument, and buffer argument. ## Image optimization (paid) - [About image stack](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/about-image-stack.md): Configure Image Stack to optimize JPG and PNG images on the fly using quality adjustment, WebP/AVIF compression, resize, and crop operations; optimized versions cache on CDN while original images remain unchanged and X-Img-Operations headers track transformations. - [Enable image stack](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/enable-image-stack.md): Enable Image Stack option for CDN resources via Gcore Support, then configure image quality (High/Medium/Low/Custom 0-100%), WebP and AVIF compression, and resize/crop parameters through CDN resource Rules with the image optimization template. ## Image stack tools - [Сonfigure image compression to WebP and AVIF](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/configure-image-compression-to-webp-and-avif.md): Enable WebP and AVIF image compression in Gcore CDN to automatically convert JPG and PNG images to modern optimized formats via Customer Portal Image optimization rules or query string parameters. - [Change image quality](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/change-image-quality.md): Configure image quality reduction in Gcore CDN Image Stack via portal settings or query string parameters (quality values - High, Medium, Low, or custom percentage) applied alongside format conversion (WebP, AVIF) or other transformations (Crop, Resize). - [Crop images](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/crop-images.md): Configure image cropping in Gcore CDN using query string parameters to specify aspect ratio, dimensions, and crop location before image delivery via the Image Stack paid feature. - [Reduce image size](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/reduce-image-size.md): Configure Resize query parameters (width, height) in image URLs to reduce JPG and PNG dimensions on Gcore CDN with automatic aspect ratio preservation or cropping via Image Stack feature. - [Possible image stack errors](https://gcore.com/docs/cdn/cdn-resource-options/image-optimization-paid/possible-image-stack-errors.md): Troubleshoot Image Stack errors by examining HTTP status codes, response headers (X-Img-Server, X-IMG-Saved-Bytes, X-IMG-Processing-Time, X-GCDN-Origin-Size), and request methods using browser developer tools to identify broken images, missing processing, or incorrect GET requests. - [Query String Forwarding: forward parameters to sub-requests](https://gcore.com/docs/cdn/cdn-resource-options/query-string-forwarding.md): Configure Query String Forwarding in Gcore CDN to copy query string parameters from parent manifest requests to nested HLS and MPEG-DASH file requests, specifying forward_from_file_types, forward_to_file_types, and forward_only_keys via portal or API. - [Determine in which regions the content will be delivered with Geobalancer for paid tariffs](https://gcore.com/docs/cdn/cdn-resource-options/determine-in-which-regions-the-content-will-be-delivered-with-geo-balancer-for-paid-tariffs.md): Configure Geobalancer to restrict content delivery to specific regions (North America, Latin America, Asia, Middle East, Australia, Africa, Europe) and set default location handler fallback regions (Asia, Near East, Middle America, Europe) for paid CDN tariffs to optimize Cache Hit Ratio. ## Rules for particular files - [Create a rule manually or from a template to configure settings for particular files](https://gcore.com/docs/cdn/cdn-resource-options/rules-for-particular-files/create-a-rule-manually-or-from-a-template-to-configure-settings-for-particular-files.md): Create CDN rules to override resource-level settings for specific file paths using URI patterns or regex, configuring cache lifetime, origin protocol, and other CDN options per rule with a maximum of five custom rules per resource. - [Create a CDN resource rule template manually or use a system one](https://gcore.com/docs/cdn/cdn-resource-options/rules-for-particular-files/create-a-cdn-resource-rule-template-manually-or-use-a-system-one.md): Create custom CDN resource rule templates with file paths, origin pull protocol (HTTP, HTTPS, Inherit from resource), and additional options, or apply system templates for video streaming (.ts, .m3u8), Let's Encrypt HTTP-01 challenge validation, and static content caching. - [Avoid indexing of your CDN resource by web crawlers](https://gcore.com/docs/cdn/cdn-resource-options/rules-for-particular-files/set-robots-txt-to-avoid-adding-to-index-by-web-crawlers.md): Configure Status code rules on CDN custom domains to return HTTP 403 Forbidden responses and prevent web crawlers from indexing duplicate content across CDN and origin domains. - [Clear CDN resource cache by URL, pattern, or all and check purge history](https://gcore.com/docs/cdn/clear-cdn-resource-cache-by-url-pattern-or-all.md): Clear CDN resource cache by URL, pattern, or all using Gcore CDN Purge API or Customer Portal, with purge history tracking and rate limits of two requests per resource per minute. ## Grafana - [View CDN statistics in Grafana](https://gcore.com/docs/cdn/grafana/view-cdn-statistics-in-grafana.md): Display CDN statistics in Grafana using the cdn-stats plugin to visualize Total Traffic, Byte Cache Hit Ratio, Edges Traffic, Shield Traffic, Origin Traffic, Total Requests, HTTP response codes (2xx, 3xx, 4xx, 5xx), Bandwidth, Cache Hit Ratio, and Shield Traffic Ratio, grouped by Clients, Resource, Region, Country, Data Center, or Vhost parameters. - [How the CDN service and its additional options are billed](https://gcore.com/docs/cdn/how-the-cdn-service-and-its-additional-options-are-billed.md): Configure CDN billing plans with monthly traffic limits, traffic overage charges, and request overage fees; traffic renews monthly and includes origin-to-CDN and CDN-to-end-user traffic. ## IP configuration options - [Bring Your Own IP](https://gcore.com/docs/cdn/ip-configuration-options/byoip.md): Enable Bring Your Own IP (BYOIP) to announce custom IP subnets from Gcore's ASN or bring your own ASN for IP address management and network customization. - [Dedicated IP](https://gcore.com/docs/cdn/ip-configuration-options/dedicated-ip.md): Enable Dedicated IP addresses or subnets to isolate sensitive content from shared IP networks and reduce reputation risk from other users' traffic. - [Load content to the CDN before users request it](https://gcore.com/docs/cdn/load-the-content-to-cdn-before-users-request-it.md): Enable CDN Prefetch to preload content into cache before user requests using file paths, supporting files 200 MB to 5 GB with maximum 100 paths per request and 1 request per minute limit. ## Logs - [Logs uploader](https://gcore.com/docs/cdn/logs/logs-uploader.md): Configure CDN Logs uploader to export request and cache behavior logs to Object Storage, S3-compatible, FTP, SFTP, or HTTP(S) destinations via Configurations, Policies, and Targets tabs with field selection, delivery frequency, and target authentication management. - [Log viewer: view and download CDN resource logs](https://gcore.com/docs/cdn/logs/log-viewer-view-and-download-cdn-resource-logs.md): View and download CDN resource logs using Log viewer with filters for time interval, client IP, HTTP method, status code, data center, and cache status; export up to 10,000 log entries per 24-hour period. ## SSL certificates - [Add an SSL certificate to deliver content over HTTPS](https://gcore.com/docs/cdn/ssl-certificates/add-an-ssl-certificate-to-deliver-content-over-https.md): Attach SSL certificates to CDN resources for HTTPS delivery using custom domains, supporting both third-party certificates and free Let's Encrypt certificates via Gcore Customer Portal. - [Configure your own SSL certificate](https://gcore.com/docs/cdn/ssl-certificates/configure-your-own-ssl-certificate.md): Upload custom SSL certificates in PEM format with certificate chain (personal certificate, intermediate CA, root CA) and private key to Gcore CDN, then attach to CDN resources for custom domains and wildcard subdomains. - [Configure Let's Encrypt certificate](https://gcore.com/docs/cdn/ssl-certificates/configure-lets-encrypt-certificate.md): Enable HTTPS with free Let's Encrypt certificates on CDN resources using HTTP-01 or DNS-01 challenge validation, with optional Gcore Managed DNS delegation to ns1.gcorelabs.net and ns2.gcdn.services for domain ownership verification. ## Terraform - [Manage CDN resources with Terraform v0](https://gcore.com/docs/cdn/terraform/manage-cdn-via-terraform.md): Create and manage Gcore CDN resources using Terraform provider v0. Covers origin groups with host and S3 origins, CDN resources with delivery options, SSL certificates (automated and manual), CA certificates for origin verification, CDN rules, rule templates, presets, account configuration, origin shielding (premium), and CDN logs uploader (premium). Uses gcore_cdn_origingroup, gcore_cdn_resource, gcore_cdn_sslcert, gcore_cdn_cacert, gcore_cdn_rule, gcore_cdn_rule_template, gcore_cdn_applied_preset, gcore_cdn_client_config, gcore_cdn_originshielding, gcore_cdn_logs_uploader_policy, gcore_cdn_logs_uploader_target, gcore_cdn_logs_uploader_config resources. - [Manage CDN resources with Terraform v2](https://gcore.com/docs/cdn/terraform/manage-cdn-via-terraform-v2.md): Create and manage Gcore CDN resources using Terraform provider v2. Covers origin groups with host and S3 sources using list syntax, CDN resources with map-style options, SSL certificates with write-only fields, CA certificates, CDN resource rules, and rule templates. Uses gcore_cdn_origin_group, gcore_cdn_resource, gcore_cdn_certificate, gcore_cdn_trusted_ca_certificate, gcore_cdn_resource_rule, gcore_cdn_rule_template resources. Key v2 changes from v0 include map-syntax options, write-only S3 credentials, and renamed certificate fields. ## Troubleshooting - [Common Setup Issues](https://gcore.com/docs/cdn/troubleshooting/common-setup-issues.md): Resolve CDN setup issues including 503 service unavailable errors from unreachable origins, ERR_TOO_MANY_REDIRECTS from HTTP-to-HTTPS redirect loops, incorrect MIME type headers causing file downloads, and Let's Encrypt SSL certificate validation failures due to DNS propagation delays. - [Resolve errors by status code for GCore CDN](https://gcore.com/docs/cdn/troubleshooting/gcore-error-status-codes.md): Resolve HTTP 403 and 404 status code errors in Gcore CDN by checking Log viewer delivery status, enabling disabled CDN resources, and adjusting security policies for Referrer, Country, IP, and User-Agent restrictions. - [Traceparent header for troubleshooting](https://gcore.com/docs/cdn/troubleshooting/traceparent-header-for-troubleshooting.md): Enable W3C Trace Context traceparent header support in Gcore CDN to track requests across services using trace-id, parent-id, trace-flags, and tracestate fields; forward traceparent headers to origin while modifying only parent-id, and access traceparent values in response headers and Raw Logs for request troubleshooting. - [Content is unavailable after a CDN resource creation: how to solve the issue](https://gcore.com/docs/cdn/troubleshooting/content-is-unavailable-after-a-cdn-resource-creation-how-to-solve-the-issue.md): Troubleshoot CDN resource content unavailability by verifying origin HTTP 200 response codes, checking CNAME record configuration in DNS settings, and validating Host Header options in CDN resource settings. - [Cache hit ratio is low: How to solve the issue](https://gcore.com/docs/cdn/troubleshooting/cache-percentage-is-low-how-to-solve-the-issue.md): Monitor cache hit ratio in Gcore CDN Statistics to identify low cache delivery efficiency; check Cache-Control and Cache response headers on edge servers using X-id header tracking to diagnose origin requests and content delivery delays. - [Content delivery speed is low: how to solve the issue](https://gcore.com/docs/cdn/troubleshooting/content-delivery-speed-is-low-how-to-solve-the-issue.md): Diagnose and resolve low CDN content delivery speed by comparing origin and CDN performance using DevTools, wget, or online speed tests, then optimize CDN-resource settings including cache hit ratio, large file delivery, and gzip/brotli compression. - [An SSL certificate isn't working: how to solve the issue](https://gcore.com/docs/cdn/troubleshooting/an-ssl-certificate-isn-t-working-how-to-solve-to-issue.md): Troubleshoot SSL certificate attachment and Let's Encrypt issuance failures by verifying certificate chain formatting, checking CDN rules don't block /.well-known/acme-challenge/ path, and confirming CNAME record configuration in DNS. - [3xx error: how to solve CDN issues with redirect](https://gcore.com/docs/cdn/troubleshooting/3xx-error-how-to-solve-cdn-issues-with-redirect.md): Resolve CDN 3xx redirect errors by configuring origin pull protocol (HTTP or HTTPS) to match origin redirect settings, updating Host Header to match the origin domain, and setting the correct Origin source for redirected domains. - [4xx error: how to solve CDN issues with the limited access and content non-existence](https://gcore.com/docs/cdn/troubleshooting/4xx-error-how-to-solve-cdn-issues-with-the-limited-access-and-content-non-existence.md): Diagnose and resolve 4xx errors in Gcore CDN by verifying origin content availability, allowlisting CDN edge IPs, configuring Origin Pull Protocol, and validating Host Header settings; use Reports, Log viewer, and Raw logs to track error sources. - [5xx error: how to solve server issues](https://gcore.com/docs/cdn/troubleshooting/5xx-error-how-to-solve-server-issues.md): Diagnose and resolve HTTP 5xx errors on CDN edge servers and origin servers by checking Gcore Status Page for incidents, verifying origin availability and response times, whitelisting CDN edge server IPs in origin ACL, and configuring correct origin pull protocol and Host Header settings in CDN resource options. ## Video CDN - [Video CDN Overview](https://gcore.com/docs/cdn/video-cdn/video-cdn-overview.md): Configure Video CDN to deliver HLS, DASH, HTTP-FLV, and MP4 video streams through Gcore CDN edge locations worldwide; requires Support approval with Client ID, domain, content type, and licensing verification for live and VOD workflows. - [HTTP-FLV Live and VOD Delivery](https://gcore.com/docs/cdn/video-cdn/flv-streaming.md): Deploy HTTP-FLV Live streaming with ultra-low latency (1-3 seconds) and high concurrency (100K+ simultaneous viewers) using Gcore CDN's dedicated FLV Live profile; configure origin to deliver FLV container with proper headers, monotonic PTS/DTS timestamps, H.264/H.265/AAC codecs, and HTTP 200 responses cached via sliding window RAM buffer. - [Common Media Client Data (CMCD)](https://gcore.com/docs/cdn/video-cdn/cmcd.md): Use Common Media Client Data (CMCD) with Gcore Video CDN to collect player-side playback and delivery metrics in query strings or request headers, improve CDN observability, and help Gcore Support investigate video playback issues. - [HLS and LL-HLS via CDN](https://gcore.com/docs/cdn/video-cdn/hls.md): Deploy HLS and LL-HLS video streams via Gcore CDN using HTTP-based adaptive streaming with master playlists, media playlists, fMP4 CMAF segments, and partial segments; configure cache rules, query parameter whitelisting, and LIVE STREAMING preset for low-latency delivery. - [Improve video delivery speed for low-traffic accounts](https://gcore.com/docs/cdn/video-cdn/improve-video-delivery-speed.md): Configure Gcore CDN cache hit ratio and time-to-first-byte (TTFB) for video delivery by monitoring cache miss behavior, cache expiration, and edge server cache warming strategies for low-traffic accounts. - [DASH and LL-DASH via CDN](https://gcore.com/docs/cdn/video-cdn/dash.md): Deploy MPEG-DASH and LL-DASH (Low-Latency DASH) streams via Gcore CDN using .mpd manifests and CMAF segments with Chunked-Proxy technology to achieve 2-4 second glass-to-glass latency for live video delivery. - [Multi-codec VOD delivery over CDN](https://gcore.com/docs/cdn/video-cdn/multi-codec-vod-delivery.md): Deliver multi-codec VOD streams including HEVC, AV1, VP9, and H.264 renditions through Gcore CDN to reduce bandwidth consumption by 25-60% depending on codec choice and device compatibility. - [Origin shielding for video delivery](https://gcore.com/docs/cdn/video-cdn/origin-shielding-for-video.md): Enable origin shielding for video CDN delivery to add a precache shield server between origin and edge locations, reducing concurrent origin requests, origin egress costs, and improving reliability during live events and VOD cache misses. - [Secure Token for Video CDN](https://gcore.com/docs/cdn/video-cdn/secure-token.md): Enable Secure Token and Query String Forwarding in Video CDN to protect HLS and MPEG-DASH streams with temporary access tokens, forwarding token parameters from master manifests to nested manifests, segments, and subtitles via directory-path token rules. - [Auto-refresh CDN secure tokens](https://gcore.com/docs/cdn/video-cdn/secure-token-auto-refresh.md): Configure CDN Secure Token auto-refresh with 60-second expiration and query string parameters or path-based tokens to prevent link sharing during live streams and pay-per-view events, supporting plain or IP-bound token validation modes. - [View statistics of CDN resources](https://gcore.com/docs/cdn/view-statistics-of-a-cdn-resource.md): View CDN resource statistics including traffic, bandwidth, response codes, cache hit ratio, requests, regional traffic distribution, image optimization WebP conversions, request time, and upstream response times via the Statistics tab, or enable Advanced Analytics for filtered reports on requests, traffic, and unique visitors by country, directory, browser, device, and operating system. --- # Gcore FastEdge > Deploy WebAssembly edge applications on Gcore CDN edge nodes using FastEdge serverless compute for HTTP request processing, A/B testing, image conversion, and custom edge logic. - [FastEdge](https://gcore.com/docs/fastedge.md): Deploy WebAssembly edge applications on Gcore CDN edge nodes using FastEdge serverless compute for HTTP request processing, A/B testing, image conversion, and custom edge logic. - [FastEdge overview](https://gcore.com/docs/fastedge/getting-started.md): Deploy WebAssembly applications on Gcore's global edge network using FastEdge for serverless execution with HTTP request/response modification, A/B testing, personalization, image conversion, and custom DNS resolving without infrastructure maintenance. ## Create apps - [Create FastEdge apps](https://gcore.com/docs/fastedge/create-apps.md): Create FastEdge HTTP and CDN applications using Rust SDK, JavaScript SDK, or Proxy-Wasm spec to run serverless code on Gcore's CDN network with custom URLs and request/response processing. - [Create FastEdge HTTP applications](https://gcore.com/docs/fastedge/getting-started/create-fastedge-apps.md): Create FastEdge HTTP applications by uploading custom WebAssembly binaries built with JavaScript SDK or Rust SDK, or by deploying preconfigured templates via Gcore Customer Portal or API. - [Extend CDN functionality with FastEdge](https://gcore.com/docs/fastedge/getting-started/integrate-cdn-with-fastedge.md): Deploy FastEdge serverless compute functions at CDN edge locations to extend content delivery with custom request/response logic, origin shielding, and dynamic content transformation. - [CDN properties](https://gcore.com/docs/fastedge/getting-started/cdn-properties.md): Access and modify HTTP request and response properties in Gcore CDN Proxy-Wasm applications via read-write properties like path, host, queryString and read-only properties like scheme, method, country, city, ASN, latitude, longitude, region, continent deciphered from client IP. - [Manage FastEdge apps](https://gcore.com/docs/fastedge/manage-apps.md): Manage FastEdge HTTP and CDN applications via the Customer Portal - start or stop applications, view metrics and logs, configure response headers, environment variables, secrets, and Edge Storage key-value storage. - [Create and manage templates](https://gcore.com/docs/fastedge/create-manage-templates.md): Create FastEdge templates with custom binary files, mandatory parameters, and Secret environment variables for HTTP and CDN applications via Customer Portal. ## Secrets Manager - [Secrets Manager](https://gcore.com/docs/fastedge/secrets-manager/manage-secrets.md): Create and manage encrypted secrets in FastEdge Secrets Manager with slot numbers and secret values, then access them in applications via JavaScript SDK and Rust SDK. - [Secrets Slots](https://gcore.com/docs/fastedge/secrets-manager/slots.md): Configure FastEdge Secrets Slots for secret rotation by storing multiple encrypted secret versions with slot indices, enabling runtime secret updates via get_secret API without deleting old values and supporting token validation against specific secret versions using slot indices or timestamps. ## Edge Storage - [How it works](https://gcore.com/docs/fastedge/kv-stores/how-it-works.md): Deploy Edge Storage as a distributed key-value store co-located with FastEdge WASM applications at every global edge location, providing sub-millisecond read latency with write-once replication to central SQL database and eventual consistency propagation within 1-2 seconds. - [Edge Storage](https://gcore.com/docs/fastedge/kv-stores/manage-kv-store.md): Create and manage key-value pairs in FastEdge Edge Storage with support for file uploads up to 1 MB, key size limits of 256 bytes, expiration dates, and edit/delete operations via Gcore Customer Portal. - [Sorted Set](https://gcore.com/docs/fastedge/kv-stores/sorted-set.md): Create and manage Sorted Sets (ZSET) in FastEdge Edge Storage via the Gcore Customer Portal, adding members with numeric scores that are automatically ordered for leaderboards and priority-based lists. - [Bloom Filter](https://gcore.com/docs/fastedge/kv-stores/bloom-filter.md): Create and manage Bloom Filters in FastEdge Edge Storage via Gcore Customer Portal to test set membership with space-efficient probabilistic data structures supporting manual value entry and file uploads up to 1 MB. - [Cache](https://gcore.com/docs/fastedge/cache.md): Cache is a POP-local, strongly consistent key-value store available to FastEdge applications at runtime for transient state such as rate-limit counters, response memoization, and idempotency checks. It is distinct from Edge Storage, which is globally replicated and durable. - [Troubleshooting](https://gcore.com/docs/fastedge/troubleshooting.md): Diagnose FastEdge application failures using HTTP status codes 530 (internal error), 531 (memory limit exceeded), 532 (timeout), and 533 (crash) to identify root causes and access FastEdge SDK Rust, JavaScript, AssemblyScript, and development tools for resolution. - [FastEdge CLI](https://gcore.com/docs/fastedge/fastedge-cli.md): Install FastEdge CLI from the FastEdge-lib repository, build the Rust-based tool, and execute local HTTP applications with commands supporting environment variables, geo headers, and request/response inspection. --- # Gcore Edge Cloud > Provision Gcore Edge Cloud resources including Virtual Machines, Bare Metal servers, managed Kubernetes, PostgreSQL, object storage, load balancers, and networking across global regions. - [Cloud](https://gcore.com/docs/cloud.md): Provision Gcore Edge Cloud resources including Virtual Machines, Bare Metal servers, managed Kubernetes, PostgreSQL, object storage, load balancers, and networking across global regions. - [About Gcore cloud](https://gcore.com/docs/cloud/about-gcore-cloud.md): Gcore Edge Cloud provides Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) with on-demand compute, databases, and applications across TIER III data centers in Manassas, Amsterdam, and Singapore, and TIER IV data center in Luxembourg. - [Billing](https://gcore.com/docs/cloud/billing.md): Configure PAYG billing for Edge Cloud resources charged per minute; manage balance top-ups, payment methods, and service suspension thresholds; track separate charges for Virtual Machines, Volumes, IP addresses (floating, virtual, reserved), snapshots, images, Windows licenses, Bare Metal servers, AI GPUs/IPUs, Managed Logging storage volume, and Function as a Service compute usage. ## Getting started - [Manage resource quotas](https://gcore.com/docs/cloud/getting-started/request-a-quota-increase.md): Check current quota limits and usage for Cloud resources by region, and request quota increases via the Customer Portal Quotas Viewer or the Gcore REST API using Python SDK, Go SDK, or curl. ## Projects - [Create and manage projects](https://gcore.com/docs/cloud/getting-started/projects/create-a-project.md): Create and manage Edge Cloud projects as isolated resource containers for Virtual Machines, volumes, and networks with per-project user permission controls via Gcore Customer Portal Projects page, list/grid view layouts, and project creation interface. ## Users - [User roles and rights](https://gcore.com/docs/cloud/getting-started/projects/users/user-roles-and-rights.md): Assign user roles and permissions across account and project scopes - Client Administrator, Project Administrator, Project User, and Project Internal Network Only User control access to Virtual Machines, Bare Metal, Volumes, Snapshots, File Shares, GPU Cloud, Managed Kubernetes, Function as a Service, Managed Logging, Networks, Firewalls, Load Balancers, and audit logs. - [Add a new user to your project](https://gcore.com/docs/cloud/getting-started/projects/users/add-a-new-user-to-your-project.md): Invite users to Gcore projects via the Customer Portal Access tab by entering email addresses and assigning Administrator, User, or Viewer roles; invitations trigger account creation links for new users or access notifications for existing users. - [Manage user access to your project](https://gcore.com/docs/cloud/getting-started/projects/users/manage-user-access-to-your-project.md): Manage user roles and project access by editing role assignments (User, Observer, Administrator), denying access via Delete role button, and restoring access by reassigning roles in project settings. - [View user actions](https://gcore.com/docs/cloud/getting-started/projects/users/view-user-actions.md): View user action logs in Gcore Edge Cloud Control Panel filtered by resource ID, project, action type, resource group, and time range; logged actions include attachment, creation, deletion, detaching, downloading, hard reboot, Load Balancer operations, reboot, request, resize, resumption, retyping, start, stop, suspending, and updating. - [Cost reports](https://gcore.com/docs/cloud/getting-started/view-statistics-on-expenses.md): View Cloud resource usage and costs via Cost Report (Pay-As-You-Go rates) or Reservation Cost Report (with resource commitment discounts), filtered by Project, Region, Resource type, and consumption period, accessible through portal and Cost Reports API. ## Resource reservation - [About resource reservation](https://gcore.com/docs/cloud/getting-started/resource-reservation/about-resource-reservation.md): Create long-term resource reservations for Gcore Cloud servers with 1-year or 3-year terms at discounted rates, selecting region, server type, Windows License option, quantity, and reservation period via the Reservations portal. ## Virtual Machines - [Types of Virtual Machines](https://gcore.com/docs/cloud/virtual-instances/types-of-virtual-machines.md): Configure Gcore Virtual Machine types including Standard, GPU, CPU, Memory, High-frequency, Basic VM, TPM, and Network optimised instances with network bandwidth specifications up to 1 Gbps and traffic policies. - [Create a Virtual Machine](https://gcore.com/docs/cloud/virtual-instances/create-an-instance.md): Create a Linux or Windows Virtual Machine in Gcore Cloud via Customer Portal or REST API. - [Customize the initial setup for your Virtual Machine](https://gcore.com/docs/cloud/virtual-instances/customize-initial-setup-for-your-instance.md): Configure Virtual Machine initial setup using User Data field with cloud-init YAML syntax to set passwords, create users, configure groups, add SSH keys, install packages, and configure network interfaces via Gcore portal, API, or Terraform. - [Check the operational status of your Virtual Machine](https://gcore.com/docs/cloud/virtual-instances/check-the-operational-status-of-your-instance.md): Retrieve Virtual Machine operational status via the Customer Portal Status column or via the REST API using GET /cloud/v1/instances to read ACTIVE, BUILD, SHUTOFF, and ERROR status values. - [Enable root user on a Linux VM](https://gcore.com/docs/cloud/virtual-instances/enable-root-user-on-a-linux-vm.md): Enable root user access on Linux VMs using sudo, sudo su, sudoers configuration, and su commands for privilege escalation and superuser shell sessions. ## Connect - [Connect to a Virtual Machine via the Gcore customer portal](https://gcore.com/docs/cloud/virtual-instances/connect/connect-to-your-instance-via-control-panel.md): Connect to Gcore Virtual Machines via VNC console in the Customer Portal using password authentication for Windows and Linux instances, or SSH keys for Linux VMs without configured passwords. ## Connect via SSH - [Connect to a Virtual Machine via SSH](https://gcore.com/docs/cloud/virtual-instances/connect/connect-via-ssh.md): Connect to Gcore Virtual Machines via SSH using public-private key pairs or password authentication; configure SSH keys, firewall rules for TCP port 22, and establish remote login sessions to Linux instances. - [Configure and manage SSH keys](https://gcore.com/docs/cloud/virtual-instances/connect/connect-to-your-instance-via-ssh.md): Generate and manage SSH key pairs in Gcore Customer Portal for Virtual Machine authentication, including public key storage, private key download, and key naming with Latin characters, underscores, spaces, and dots (3-63 characters). - [Convert an SSH key to PPK format](https://gcore.com/docs/cloud/ssh-keys/convert-an-ssh-key-from-pem-to-ppk.md): Convert SSH keys to PPK format using PuTTYgen for PuTTY connections to Gcore Virtual Machines, supporting private and public key export. - [Establish SSH connection to a Virtual Machine](https://gcore.com/docs/cloud/virtual-instances/connect/connect-via-ssh/establish-ssh-connection-to-an-instance.md): Establish SSH connection to Virtual Machine instances using SSH key pairs or password authentication via terminal, WSL, Command Prompt, or PuTTY with floating IP address and firewall rules configured. ## Placement groups - [About placement groups](https://gcore.com/docs/cloud/virtual-instances/placement-groups/about-placement-groups.md): Configure placement groups with Affinity, Anti-affinity, or Soft anti-affinity policies to control Virtual Machine colocation on physical servers for performance optimization or fault tolerance. - [Configure a placement group](https://gcore.com/docs/cloud/virtual-instances/placement-groups/configure-a-placement-group.md): Create and manage Virtual Machine placement groups via the Customer Portal or REST API, covering affinity and anti-affinity policies, VM assignment during creation, and moving VMs between groups. ## Volumes - [Volumes](https://gcore.com/docs/cloud/virtual-instances/volumes/about-volumes.md): Create boot and regular volumes in Gcore Cloud with High IOPS SSD, Standard, SSD Low-Latency, or deprecated Cold and Ultra types; boot volumes store OS and are required for VM startup, while regular volumes provide general-purpose storage with configurable IOPS limits, bandwidth, and triple data replication. - [Create and configure a volume](https://gcore.com/docs/cloud/virtual-instances/volumes/create-and-configure-volumes.md): Create and configure block storage volumes in Gcore Cloud via Customer Portal or REST API, including creating, attaching, detaching, resizing, and deleting volumes. - [Monitor load on a specific node](https://gcore.com/docs/cloud/virtual-instances/monitor-load-and-performance-of-your-instance.md): Monitor Virtual Machine performance metrics including CPU Utilization, RAM Utilization, Network BPS ingress/egress, Network PPS ingress/egress, and Disk IOPS read/write operations via the Monitoring tab. ## Snapshots - [Take a snapshot of your file system](https://gcore.com/docs/cloud/virtual-instances/snapshots/take-a-snapshot-of-your-file-system.md): Create, view, and delete volume snapshots in Gcore Cloud via the Customer Portal or REST API, including Python SDK and Go SDK examples. - [Set up automatic snapshot creation](https://gcore.com/docs/cloud/virtual-instances/snapshots/set-up-automatic-snapshot-creation.md): Create Snapshot Schedules to automate volume snapshot creation at specified days, hours, minutes, or intervals, with configurable name templates using {volume_id} variables and maximum snapshot retention limits. ## Troubleshooting - [Troubleshoot issues with an SSH connection](https://gcore.com/docs/cloud/virtual-instances/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection issues to Gcore Virtual Machines including root login permission denied errors, SSH key authentication setup, multiple SSH key management, and VNC console password recovery when private keys are lost. ## Bare Metal servers - [About Bare Metal](https://gcore.com/docs/cloud/bare-metal-servers/about-bare-metal-servers.md): Deploy dedicated physical Bare Metal servers across 25 global locations with exclusive access to CPU, memory, and networking; configure via Gcore Portal, API, or Terraform with LACP-aggregated network bonds, public/private interfaces, and choice of Ubuntu, CentOS, Debian, Windows, or custom ISO images. - [Types of Bare Metal servers](https://gcore.com/docs/cloud/bare-metal-servers/types-of-bare-metal-servers.md): Configure Gcore Bare Metal servers by type - High-frequency servers with Intel Xeon E-2388G or Ryzen 5950x CPUs for low-latency gaming and real-time analytics; Infrastructure servers with dual Silver 4214R or 4314 CPUs for databases and virtualization; Basic servers with Intel Xeon E-2236 for lightweight applications and development environments. - [Create a Bare Metal server](https://gcore.com/docs/cloud/bare-metal-servers/create-a-bare-metal-server.md): Create a Bare Metal server on dedicated physical hardware via Customer Portal or REST API. - [Connect to your Bare Metal via SSH](https://gcore.com/docs/cloud/bare-metal-servers/connect-to-your-bare-metal-server-via-ssh.md): Connect to Bare Metal servers via SSH using RSA key pairs (2048 bits) generated with ssh-keygen or PuTTYgen, or authenticate with password; configure firewall rules to permit incoming SSH traffic. ## Troubleshooting - [Troubleshoot issues with an SSH connection](https://gcore.com/docs/cloud/bare-metal-servers/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection issues to Bare Metal servers including root login permission denied errors, missing console passwords, and lost SSH keys; configure SSH key authentication, add multiple public keys via Customer Portal, and access servers using OS-specific default usernames (ubuntu, debian, fedora, centos). ## Advanced DDoS protection - [About advanced DDoS protection for Bare Metal](https://gcore.com/docs/cloud/bare-metal-servers/advanced-ddos-protection/about-advanced-ddos-protection-for-bare-metal-servers.md): Enable Advanced DDoS protection for Bare Metal servers with threat mitigation system (TMS) traffic redirection, ACL configuration, L3/L4/L7 attack filtering, and always-on mode to maintain server uptime without IP blocking during attacks. - [Activate advanced DDoS protection for Bare Metal](https://gcore.com/docs/cloud/bare-metal-servers/advanced-ddos-protection/activate-advanced-ddos-protection-for-bare-metal-servers.md): Enable Advanced DDoS protection on Bare Metal server network interfaces with public IP addresses by selecting a protection profile template during server creation or via the Networking tab interface configuration. ## Images - [About images](https://gcore.com/docs/cloud/images/about-images.md): Create Virtual Machine boot volumes from images containing disk file system structure, data, and pre-installed operating systems or software. - [Upload an image to the storage](https://gcore.com/docs/cloud/images/upload-an-image-to-the-storage.md): Upload images to Gcore Cloud storage via URL import, supporting raw, vhd, vhdx, vdi, ploop, qcow2, and ami formats with VirtIO drivers and cloud-init package for Virtual Instances, Bare Metal, Virtual GPU Clusters, and Baremetal GPU Clusters using x86 or ARM architecture selection and VM quick start toggle configuration. ## Networking - [Create and manage a network](https://gcore.com/docs/cloud/networking/create-and-manage-a-network.md): Create a private network with a subnet to connect Virtual Machines within a region, and manage it via the Gcore REST API using Python SDK, Go SDK, or curl. - [Create and manage a subnetwork](https://gcore.com/docs/cloud/networking/create-and-manage-a-subnetwork.md): Create, update, and delete subnetworks in Gcore Cloud via the Customer Portal or REST API using POST /cloud/v1/subnets, with CIDR ranges, DHCP, DNS servers, and host routes configuration. - [Create and manage a router](https://gcore.com/docs/cloud/networking/create-and-manage-a-router.md): Create and configure Cloud Router with static routes, SNAT, and subnet interfaces via the Customer Portal or REST API using POST /cloud/v1/routers to dynamically exchange routes between networks. ## IP address - [Create and configure a floating IP address](https://gcore.com/docs/cloud/networking/ip-address/create-and-configure-a-floating-ip-address.md): Reserve a floating IP address in Gcore Cloud and assign it to a Virtual Machine, Bare Metal server, or Load Balancer using the Customer Portal or REST API. - [Create and configure a reserved IP address](https://gcore.com/docs/cloud/networking/ip-address/create-and-configure-a-reserved-ip-address.md): Reserve a public or private fixed IP address in Gcore Cloud via the Customer Portal or REST API, and use the port ID to assign it to a Virtual Machine, Bare Metal server, or Load Balancer. - [Create and configure a virtual IP address](https://gcore.com/docs/cloud/networking/ip-address/create-and-configure-a-virtual-ip-vip-address.md): Reserve a virtual IP address (VIP) via API or Customer Portal, connect VM ports to share the address, enable or disable VIP mode on existing reserved IPs, and configure VRRP-based failover using Keepalived. - [Difference between virtual, floating, and reserved IP addresses](https://gcore.com/docs/cloud/networking/ip-address/difference-between-virtual-floating-and-reserved-ip-addresses.md): Compare Floating IP, Reserved IP, and Virtual IP address types in Gcore Cloud by assignment scope (single VM vs. multiple VMs), failover capability, billing when unassigned, and use cases for external access, high availability, and Bare Metal support. - [Configure an allowed address pair](https://gcore.com/docs/cloud/networking/ip-address/configure-an-allowed-address-pair.md): Assign additional IP addresses to a Virtual Machine's private network interface port via the allowed address pairs API, enabling traffic routing to multiple IPs on a single MAC address with support for up to 10 pairs per port. ## Load balancers - [Create and configure a load balancer](https://gcore.com/docs/cloud/networking/create-and-configure-a-load-balancer.md): Create and configure a Load Balancer with region selection, computing configuration (vCPU, GiB), network type (Public, Private), IP family (IPv4, IPv6, Dual), reserved IP assignment, preferred connectivity method (L2 or L3), listeners, and pools via Customer Portal or REST API. - [Add TLS certificates to a load balancer](https://gcore.com/docs/cloud/networking/load-balancers/add-certificates-to-load-balancer.md): Upload TLS certificates to Gcore Secrets Manager and attach them to TERMINATED HTTPS load balancer listeners to enable SNI-based multi-domain termination; create listeners with a default certificate and add per-domain SNI certificates via the REST API. - [Configure mutual TLS authentication](https://gcore.com/docs/cloud/networking/load-balancers/configure-mtls-authentication.md): Configure mutual TLS authentication between Gcore Load Balancers and backend servers using PKCS12 listener certificates, PEM CA certificates, and optional client certificates for mTLS pool configuration via API endpoints. - [Manage load balancers](https://gcore.com/docs/cloud/networking/load-balancers/manage-load-balancers.md): List, inspect, rename, update tags, initiate failover, and delete Load Balancers via the Customer Portal or Gcore REST API with Python SDK, Go SDK, and curl examples. - [Logging for load balancers](https://gcore.com/docs/cloud/networking/load-balancers/logging-for-load-balancers.md): Enable Logging for Load Balancers to collect and store access logs via Gcore Logging service; configure namespace, topic, and retention period; verify guaranteed throughput between Load Balancer regions (Amsterdam, Frankfurt, Tokyo, Istanbul, London, Warsaw, Dubai, Almaty) and Logging destination regions. - [Use annotations for load balancers](https://gcore.com/docs/cloud/networking/load-balancers/use-annotations-for-load-balancers.md): Configure Load Balancer annotations in Gcore Managed Kubernetes to set load balancer type (internal or external), flavor, shared name, floating IP address, fixed IP address, listener connection limits, and pool node selectors via kubectl or service manifest. - [Monitoring for load balancers](https://gcore.com/docs/cloud/networking/load-balancers/monitoring-for-load-balancers.md): Enable Prometheus listener on load balancers to expose metrics endpoint for scraping with Prometheus and Grafana, configurable via Customer Portal with Protocol selection, Port, Connection limit, and security options including CIDR IP ranges, Basic Auth, SSL/TLS certificates, and mTLS authentication. - [Add and configure a firewall](https://gcore.com/docs/cloud/networking/add-and-configure-a-firewall.md): Create and configure security groups and firewall rules for Virtual Machines via Customer Portal or REST API. - [Bring Your Own IP (BYOIP)](https://gcore.com/docs/cloud/networking/byoip.md): Configure Bring Your Own IP (BYOIP) to announce customer-owned public IP address ranges via Gcore ASN or customer ASN (BYOASN) using Letter of Authorization, Route Object (IRR), RPKI ROA, and CIDR prefix registration with Regional Internet Registry. ## File shares - [About file shares](https://gcore.com/docs/cloud/file-shares/about-file-shares.md): Create and manage NFS file shares across Virtual Machines, Bare Metal servers, and Kubernetes pods using the NFS protocol, with support for access rules, snapshots, persistent volumes with RWX mode, and on-demand scaling. - [Configuring file shares](https://gcore.com/docs/cloud/file-shares/configure-file-shares.md): Create NFS-based file shares and mount them to Virtual Machines via Customer Portal or REST API. - [Migrate data from S3 and EFS to Gcore](https://gcore.com/docs/cloud/file-shares/how-to-migrate-data-from-s3.md): Migrate data from Amazon S3 and EFS to Gcore Object Storage and File Shares using rclone CLI tool with AWS IAM credentials, S3 bucket configuration, and NFS mount paths. ## Managed Kubernetes - [About GCore Managed Kubernetes](https://gcore.com/docs/cloud/kubernetes/about-gcore-kubernetes.md): Deploy Gcore Managed Kubernetes clusters on Virtual Machines or Bare Metal servers with autoscaling, self-healing, PersistentVolumeClaims storage, Nginx ingress controller networking, and 99.99% SLA backed by Cluster API. - [Bare Metal Kubernetes](https://gcore.com/docs/cloud/kubernetes/bare-metal-kubernetes.md): Deploy Kubernetes worker nodes on Bare Metal servers via Managed Kubernetes to eliminate virtualization layers and gain direct hardware access, improved performance, enhanced security isolation, higher network bandwidth, and lower disk latency. ## Clusters - [Create a Kubernetes cluster](https://gcore.com/docs/cloud/kubernetes/clusters/create-a-kubernetes-cluster.md): Create a Kubernetes cluster by selecting region, version, and configuring node pools with flavor (Standard, vCPU, Memory, High Frequency), disk type (High IOPS SSD, Standard, SSD Low Latency), disk size in GiB, minimum/maximum nodes for autoscaling, and worker node type (Virtual Machine or Bare Metal). Includes REST API, Python SDK, and Go SDK examples. - [Upgrade a Kubernetes cluster](https://gcore.com/docs/cloud/kubernetes/clusters/upgrade.md): Upgrade a Kubernetes cluster to a newer version via the Gcore REST API or Customer Portal using a rolling update that replaces worker nodes sequentially without stopping them all at once. ## Connect - [Connect to your nodes via SSH](https://gcore.com/docs/cloud/kubernetes/clusters/connect/connect-to-your-nodes-via-ssh-using-a-floating-ip-address.md): Assign floating IP addresses to Kubernetes cluster nodes and connect via SSH using the floating IP address and private key authentication. - [Install kubectl and connect to a Kubernetes cluster](https://gcore.com/docs/cloud/kubernetes/clusters/connect/install-kubectl-and-connect-to-a-kubernetes-cluster.md): Install kubectl command-line tool on Windows, configure PATH environment variable, create .kube directory, and add kubeconfig file to connect to Kubernetes clusters via API requests. - [Secure Kubernetes cluster with OpenID Connect](https://gcore.com/docs/cloud/kubernetes/clusters/secure-cluster-with-oidc.md): Configure OpenID Connect (OIDC) authentication for Gcore Managed Kubernetes clusters by setting Issuer URL, Client ID, username claim, groups claim, required claims, and signing algorithms to enable centralized SSO access control. ## Autoscaling - [About autoscaling](https://gcore.com/docs/cloud/kubernetes/clusters/autoscaling/about-autoscaling.md): Configure Kubernetes node pool autoscaling with minimum and maximum node limits; autoscaling deploys nodes when pods exceed available resources and removes idle nodes after 20 minutes of inactivity. - [Change autoscaling limits](https://gcore.com/docs/cloud/kubernetes/clusters/autoscaling/change-autoscaling-limits.md): Configure minimum and maximum node counts for Kubernetes cluster autoscaling pools via the Cloud portal Pools section. - [Create and configure a pool](https://gcore.com/docs/cloud/kubernetes/clusters/autoscaling/create-a-new-pool-in-cluster.md): Create and configure Kubernetes pools with node count autoscaling limits, worker node type selection (VM or Bare Metal), flavor, volume size, volume type, placement policy (affinity, anti-affinity soft, anti-affinity hard), labels, taints, tolerations, autohealing, and public IPv4 address assignment. - [Advanced cluster autoscaler settings](https://gcore.com/docs/cloud/kubernetes/clusters/autoscaling/advanced-cluster-autoscaler-settings.md): Configure Kubernetes cluster autoscaler advanced settings including scan interval, node group expander strategy (random, most-pods, least-waste, price, priority, grpc), max node provision time, pod scale-up delay, unready node thresholds, and scale-down behavior with post-addition and post-deletion delays. - [Configure GPU autoscaling for Kubernetes](https://gcore.com/docs/cloud/kubernetes/clusters/autoscaling/configure-gpu-autoscaling-for-kubernetes.md): Configure Kubernetes Event-Driven Autoscaling (KEDA) to automatically scale GPU resources in Gcore Managed Kubernetes clusters based on GPU utilization, using Bare Metal worker pools with GPU-optimized flavors and minimum/maximum node specifications. - [Add users with limited rights to a Kubernetes cluster](https://gcore.com/docs/cloud/kubernetes/clusters/add-users-with-limited-rights-to-a-kubernetes-cluster.md): Create Kubernetes service accounts with namespace-scoped RBAC permissions and generate kubeconfig files for limited user access via kubectl and Role bindings. - [Monitor load on a specific node](https://gcore.com/docs/cloud/kubernetes/monitor-load-on-a-specific-node.md): Monitor Kubernetes node CPU Utilization, RAM Utilization, Network Traffic, and Network Packets metrics via the Monitoring tab in Gcore Cloud portal, with configurable time period and data refresh frequency. ## Networking - [About networking in Kubernetes](https://gcore.com/docs/cloud/kubernetes/networking/about-networking-in-kubernetes.md): Configure Kubernetes Services, Ingress objects, and Ingress Controllers to route internal and external traffic to pods using single IP addresses, path-based rules, and load balancing across pod replicas. - [Install nginx Ingress controller](https://gcore.com/docs/cloud/kubernetes/networking/install-and-set-up-the-nginx-ingress-controller.md): Deploy nginx Ingress Controller on Gcore Managed Kubernetes using Helm, which automatically provisions a Load Balancer resource for routing external traffic to cluster services via Ingress manifests. - [Use Nginx Ingress Controller](https://gcore.com/docs/cloud/kubernetes/networking/use-the-nginx-ingress-controller.md): Create Ingress objects with Nginx ingressClassResource, specifying Service name, port, URL path, and apply via kubectl to route traffic through Nginx Ingress Controller. ## Storage - [Create a PVC and bind to a pod](https://gcore.com/docs/cloud/kubernetes/storage/create-a-pvc-and-bind-it-to-a-pod.md): Create PersistentVolumeClaim (PVC) resources in Gcore Managed Kubernetes by defining StorageClass with disk types (standard, ssd_highiops, ssd_lowlatency), then binding PVC to pods using kubectl with accessModes, storage capacity, and volumeBindingMode parameters. - [Configure NFS CSI driver for Managed Kubernetes](https://gcore.com/docs/cloud/kubernetes/storage/configure-nfs-csi-driver-for-kubernetes.md): Configure NFS CSI driver to dynamically provision and attach Gcore File Shares as persistent volumes in Managed Kubernetes clusters using StorageClass, PersistentVolumeClaim, and NFS protocol within the same project and network. - [Troubleshooting a node in a "Not Ready" state](https://gcore.com/docs/cloud/kubernetes/troubleshooting-not-ready-state.md): Diagnose Kubernetes nodes in "Not Ready" state by querying node conditions (OutOfDisk, MemoryPressure, DiskPressure, Ready), checking Capacity and Allocatable resources, and examining Kubelet logs for certificate, authentication, and network errors via kubectl describe node and journalctl commands. ## Managed PostgreSQL - [About managed PostgreSQL](https://gcore.com/docs/cloud/managed-database-postgresql.md): Deploy Gcore Managed PostgreSQL servers with configurable flavor, vCPU/RAM, storage capacity, connection pooler mode, and volume type; supports PostgreSQL 13, 14, and 15 with high availability via synchronous replication, IP access control lists, and multi-region data center placement. - [Manage a PostgreSQL server](https://gcore.com/docs/cloud/managed-database-postgresql/manage-postgresql-servers.md): Create a managed PostgreSQL cluster in Gcore Cloud via Customer Portal or REST API. - [Backup and restore PostgreSQL database for Managed PostgreSQL using external utilities](https://gcore.com/docs/cloud/managed-database-postgresql/backup-and-restore-postgresql-database-for-gcore-managed-database-for-postgresql-using-external-utilities.md): Backup and restore Managed PostgreSQL databases using pg_dump and pg_restore utilities with SQL, TAR, custom, and directory formats; retrieve connection credentials (hostname, username, password, port) from Customer Portal. ## Secrets manager - [Configure secrets for HTTPS load balancer](https://gcore.com/docs/cloud/secrets-manager/upload-a-pkcs12-file.md): Create SSL/TLS secrets in Gcore Secrets Manager by uploading PKCS12 files or manually entering certificate, certificate chain, and private key for HTTPS Load Balancer listeners. ## Function as a service - [About Function as a Service](https://gcore.com/docs/cloud/faas/about-function-as-a-service.md): Deploy serverless functions via Gcore FaaS using HTTP endpoints, Kubernetes pods, zero-scaler for automatic scaling from 0 pods with configurable timeout periods, and auto-scaler for maintaining minimum pod replicas with CPU and memory allocation. - [Authenticate to functions with API keys](https://gcore.com/docs/cloud/faas/authenticate-to-functions-with-api-keys.md): Create and manage API keys for Gcore Functions to authenticate endpoint access, configure expiration dates, specify authorized functions, and handle key rotation via the Cloud portal. - [Code examples for supported FaaS runtimes](https://gcore.com/docs/cloud/faas/code-examples-for-supported-faas-runtimes.md): Create FaaS functions in .NET, Go, Java, Node.js, and Python runtimes with code examples for basic handlers, dependency management via .csproj/go.mod/pom.xml/package.json/requirements.txt, and request/response object access through event parameters. ## Container as a service - [About container as a service](https://gcore.com/docs/cloud/caas.md): Deploy containerized applications in Gcore Container as a Service across supported regions using container images, managed via customer portal or REST API without Kubernetes or VM infrastructure management. - [Create a container](https://gcore.com/docs/cloud/caas/create-a-container.md): Deploy containerized applications in Gcore Container as a Service via Customer Portal or REST API. - [Build and deploy containers to CaaS via GitHub actions](https://gcore.com/docs/cloud/caas/build-and-deploy-containers-to-caas-via-github-actions.md): Deploy containers to Gcore Container as a Service via GitHub Actions workflow using the deploy-container action with required fields - API token, project ID, region ID, container name, image name, and optional parameters for port, description, environment variables, flavor, scale-down duration, minimum/maximum instances. - [Manage containers](https://gcore.com/docs/cloud/caas/manage-containers.md): Get status, update configuration, stop, start, retrieve logs, and delete CaaS containers via the Customer Portal or REST API using GET, PATCH, and DELETE requests on the /cloud/v1/caas/{project_id}/{region_id}/containers endpoint. ## Container registry - [Container registry](https://gcore.com/docs/cloud/container-registry.md): Create and manage OCI-compatible Docker image registries with per-user push and pull permissions, accessible via Docker CLI, API, and Gcore Customer Portal for use with Everywhere Inference, Container as a Service, and Managed Kubernetes. - [Create a Container Registry](https://gcore.com/docs/cloud/container-registry/create-container-registry.md): Create a Container Registry, add registry users with configurable permissions and credential expiration, and push or pull OCI-compatible images via the Customer Portal or REST API using Python and Go SDK. - [Manage container registries](https://gcore.com/docs/cloud/container-registry/manage-container-registries.md): Manage Container Registry storage limits, repositories, artifacts, tags, and users via the Customer Portal or REST API using Python and Go SDK. ## Managed logging - [About managed logging](https://gcore.com/docs/cloud/logging-as-a-service/about-logging-as-a-service.md): Configure Managed Logging to collect logs from Virtual Machines and Bare Metal servers using Kafka-compatible log shippers like Fluent Bit, Filebeat, or Logstash, then access and analyze logs via OpenSearch Dashboards with support for text/JSON format, up to 225 JSON fields, and 1 MB maximum message size. - [Configure logging and view your logs](https://gcore.com/docs/cloud/logging-as-a-service/configure-logging-and-view-your-logs.md): Configure Gcore Managed Logging by selecting a region, creating a human-readable namespace (2-32 lowercase alphanumeric characters), creating Kafka topics, generating credentials, and connecting log shippers (Fluent Bit, Filebeat, Logstash) with Kafka endpoints to export logs to OpenSearch Dashboards with @timestamp indexing. ## Install a log shipper - [Install and configure Filebeat](https://gcore.com/docs/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-filebeat.md): Configure Filebeat log shipping with input sources (file paths, TCP, UDP, syslog) and output.kafka destination parameters (hosts, topic, sasl.mechanism, sasl.username, password, ssl.enabled) to forward logs to Gcore Managed Logging via Kafka endpoint. - [Install and configure Fluent Bit](https://gcore.com/docs/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-fluent-bit.md): Configure Fluent Bit input and output sections with tail data source, Kafka brokers endpoint, topic name, and SASL authentication parameters (rdkafka.security.protocol, rdkafka.sasl.mechanism, rdkafka.sasl.username, rdkafka.sasl.password) to ship logs to Gcore Managed Logging via OpenSearch Dashboards. - [Install and configure Fluentd](https://gcore.com/docs/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-fluentd.md): Configure Fluentd with Kafka Integration Plugin to stream logs to Gcore Managed Logging using brokers, username, password, default_topic, scram_mechanism, sasl_over_ssl, and fluent-plugin-kafka output plugin. - [Install and configure Logstash](https://gcore.com/docs/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-logstash.md): Configure Logstash with Kafka output plugin to send logs to Gcore Managed Logging using topic_id, bootstrap_servers, sasl.mechanism, security_protocol, sasl_jaas_config, key_serializer, and value_serializer parameters. - [Prometheus exporter](https://gcore.com/docs/cloud/logging-as-a-service/prometheus-exporter.md): Configure Prometheus targets to scrape OpenSearch index metrics from Managed Logging via HTTPS Basic Authentication using the Prometheus exporter endpoint, exposing gauge metrics for document indexing, query cache, search scrolls, segment memory, and shard statistics. - [View GCore managed logging logs in Grafana with OpenSearch plugin](https://gcore.com/docs/cloud/logging-as-a-service/view-opensearch-logs-in-Grafana.md): Configure Gcore Managed Logging integration with Grafana using the OpenSearch Grafana Data Source plugin, setting HTTP parameters (URL, Access, Allowed cookies, Timeout) and Basic authentication credentials to display logs from OpenSearch Dashboards. ## Terraform - [Manage Cloud resources via Terraform v0](https://gcore.com/docs/cloud/manage-cloud-via-terraform.md): Create and manage Gcore Cloud resources — Virtual Machines, Bare Metal servers, Kubernetes clusters, Load Balancers, and networks — using Terraform provider v0. - [Manage Cloud resources via Terraform v2](https://gcore.com/docs/cloud/manage-cloud-via-terraform-v2.md): Create and manage Gcore Cloud resources — Virtual Machines, Bare Metal servers, Kubernetes clusters, Load Balancers, networks, volumes, security groups, and IP addresses — using Terraform provider v2. - [Manage cloud resources via Ansible](https://gcore.com/docs/cloud/manage-cloud-via-ansible.md): Configure Gcore Cloud resources using Ansible Galaxy Collection modules and plugins for provisioning, deploying, and orchestrating instances, volumes, networks, and other cloud services via playbooks with API key authentication and region/project parameters. ## Use cases - [Set up a mailing server in GCore cloud VM](https://gcore.com/docs/cloud/use-cases/set-up-a-mailing-server-in-gcore-cloud-vm.md): Configure Postfix and Dovecot mail server components on Gcore Cloud VM with SMTP port 25 access, SSL/TLS parameters, mailbox creation, and DNS records for email delivery on Ubuntu and Debian. --- # Gcore AI > Deploy AI inference and GPU-accelerated training using Gcore AI products - Everywhere Inference for low-latency model serving at the edge and GPU Cloud for Bare Metal and Virtual Machine compute. - [Overview](https://gcore.com/docs/edge-ai.md): Deploy AI inference and GPU-accelerated training using Gcore AI products - Everywhere Inference for low-latency model serving at the edge and GPU Cloud for Bare Metal and Virtual Machine compute. - [Getting started](https://gcore.com/docs/edge-ai/getting-started.md): Deploy AI models for inference using Gcore Everywhere Inference via Customer Portal or API, or create GPU clusters for model training with Gcore GPU Cloud and bare-metal infrastructure. - [Billing](https://gcore.com/docs/edge-ai/billing.md): Configure billing for Gcore GPU Virtual Machines and Bare Metal instances charged by resource type and configuration, and Everywhere Inference resources billed per minute of compute time with monthly fee processing and service suspension on payment failure. ## GPU cloud - [About GPU Cloud](https://gcore.com/docs/edge-ai/ai-infrastructure/about-gpu-cloud.md): Deploy GPU clusters with Bare Metal GPU, Spot Bare Metal GPU, or Virtual GPU instance types, configured with NVIDIA H200, H100, A100, or L40S GPUs, InfiniBand or Ethernet interconnect, and NVMe storage for distributed LLM training, inference, and HPC workloads. - [Create a Virtual GPU cluster](https://gcore.com/docs/edge-ai/ai-infrastructure/create-a-virtual-gpu-cluster.md): Create Virtual GPU clusters with configurable node count, GPU models, flavors, network boot disks, local data disks, optional network data disks, file share integration, and InfiniBand networking in Gcore GPU Cloud. - [Manage a Virtual GPU cluster](https://gcore.com/docs/edge-ai/ai-infrastructure/manage-a-virtual-gpu-cluster.md): Manage Virtual GPU cluster nodes, power state, volumes, and network interfaces via cluster details page tabs including Overview, Volumes, Networking, Power, Tags, and Delete operations. - [Create a Bare Metal GPU cluster](https://gcore.com/docs/edge-ai/ai-infrastructure/create-a-bare-metal-gpu-cluster.md): Create Bare Metal GPU clusters with dedicated physical servers, selecting region, GPU model, cluster type (Bare Metal GPU or Spot Bare Metal GPU), node count, and InfiniBand networking via Gcore Customer Portal GPU Cloud interface. - [Manage a Bare Metal GPU cluster](https://gcore.com/docs/edge-ai/ai-infrastructure/manage-a-bare-metal-gpu-cluster.md): Manage Bare Metal GPU cluster nodes, resize instance count, configure power states, network interfaces, and delete individual nodes or entire clusters via the Gcore Customer Portal cluster details page. - [Spot Bare Metal GPU](https://gcore.com/docs/edge-ai/ai-infrastructure/spot-bare-metal-gpu.md): Deploy Spot Bare Metal GPU clusters with discounted pricing for interruptible workloads like batch processing and testing, understanding reclamation with 24-hour notice, data persistence on file shares and object storage, and availability by region. ## Managed Kubernetes - [Overview](https://gcore.com/docs/edge-ai/managed-kubernetes/overview.md) - [Create a GPU Kubernetes cluster](https://gcore.com/docs/edge-ai/managed-kubernetes/create-a-gpu-kubernetes-cluster.md) - [Manage a GPU Kubernetes cluster](https://gcore.com/docs/edge-ai/managed-kubernetes/manage-a-gpu-kubernetes-cluster.md) ## Everywhere Inference - [Overview](https://gcore.com/docs/edge-ai/everywhere-inference.md): Deploy trained AI models on Gcore Everywhere Inference edge nodes using anycast endpoints and smart routing to achieve low-latency inference across global regions with automatic failover. - [Application Catalog](https://gcore.com/docs/edge-ai/everywhere-inference/application-catalog.md): Browse and deploy pre-built open-source AI models from the Gcore Everywhere Inference Application Catalog, including text LLMs, image generation, speech recognition, text embedding, and other model categories. ## AI models - [Deploy a model from the Application Catalog](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/deploy-from-catalog.md): Deploy a pre-built open-source AI model from the Gcore Everywhere Inference Application Catalog by selecting an application, choosing compute resources and regions, and configuring deployment settings in the Create Deployment form. - [Prepare a custom AI model for deployment](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/prepare-a-custom-ai-model-for-deployment.md): Prepare custom AI models for deployment by containerizing with vLLM or Diffusers, optimizing via quantization and pruning, building Docker images from Hugging Face models, and pushing to a container registry for inference serving. - [Deploy a custom model](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/deploy-a-custom-model.md): Deploy a custom AI model to Gcore Everywhere Inference using a Docker container image from a public or private registry, with configurable compute resources, routing regions, autoscaling, health checks, and optional API key authentication. - [Manage AI model deployments](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/manage-ai-model-deployments.md): Manage AI model deployments in Everywhere Inference by viewing deployment status, endpoint URLs, replica counts, and logs; navigate to deployment details to modify settings such as routing placement, flavor, and pod counts; delete deployments from the action menu. - [Query a deployed model](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/query-deployed-model.md): Send inference requests to a deployed Everywhere Inference model using curl, Python OpenAI SDK, or JavaScript. Covers finding the endpoint URL, forming chat completion requests, multi-turn conversations, streaming, and key request parameters. - [Chat with a model via Open WebUI](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/chat-with-open-webui.md): Deploy a Gcore Everywhere Inference model with Open WebUI enabled and interact with it through a browser-based chat interface. Covers enabling the Open WebUI module during deployment, accessing the chat UI, creating an admin account, and starting a conversation. - [Translate text with Llama 3.2](https://gcore.com/docs/edge-ai/everywhere-inference/ai-models/translate-text-with-llama.md): Use a deployed Llama 3.2 model on Gcore Everywhere Inference to translate text between languages. Covers the system prompt pattern, request parameters, curl, Python, and JavaScript code examples, edge case handling, and output style control. ## Container image registries - [Add a container image registry](https://gcore.com/docs/edge-ai/everywhere-inference/container-image-registries/add-a-registry.md): Add a private container image registry to Gcore Everywhere Inference. Covers what a registry is, how credentials work, registry URLs for Docker Hub, Hugging Face, and GitHub Container Registry, and how the registry connects to a deployment. - [Manage container image registries](https://gcore.com/docs/edge-ai/everywhere-inference/container-image-registries/manage-registries.md): View, edit, and delete container image registries in Gcore Everywhere Inference. Covers how registries are used in deployments, editing authentication credentials, and deleting a registry. ## API keys - [Inference deployment with API key authentication](https://gcore.com/docs/edge-ai/everywhere-inference/api-keys/create-inference-deployment-with-auth.md): Set up API key authentication for an Everywhere Inference deployment by creating a project-level API key, linking it to a deployment, and including the key in the X-API-Key header of every inference request. ## Quotas - [Request a quota increase](https://gcore.com/docs/edge-ai/everywhere-inference/quotas/request-quota-increase.md): Request a quota increase for Gcore Everywhere Inference by selecting GPU or CPU resources in the Quotas Viewer, entering a use case description, and submitting the request. Track request status in Quotas Request History. - [Quotas Request History](https://gcore.com/docs/edge-ai/everywhere-inference/quotas/quotas-request-history.md): View the history of quota increase requests for Gcore Everywhere Inference, including request status, resource type, and requested amounts, in the Quotas Request History page. --- # Gcore Gclaw > Managed OpenClaw service with built-in inference for launching AI agents instantly. - [Gclaw](https://gcore.com/docs/gclaw.md): Managed OpenClaw service with built-in inference for launching AI agents instantly. - [Getting started](https://gcore.com/docs/gclaw/getting-started.md): Create and launch a Gclaw AI assistant instance in the Gcore Customer Portal, access the chat interface, and manage instance settings including Restart Instance, Backup Config, Restore Config, and Recreate Instance operations. - [Manage instance](https://gcore.com/docs/gclaw/manage-instance.md): Manage Gclaw instance restart, backup, restore, and recreation operations via Settings panel; configure data persistence for workspace files, configuration, API keys, skills, and chat history across restart and recreate actions. - [Configure API keys](https://gcore.com/docs/gclaw/api-keys.md): Configure API keys for Gclaw OpenClaw skills including OpenAI, Spotify, Brave Search, GitHub, and Notion by providing credentials directly in the chat interface for secure storage in instance configuration. ## Integrations - [Connect Telegram](https://gcore.com/docs/gclaw/connect-telegram.md): Configure Telegram bot integration with Gclaw AI assistant by creating a bot via BotFather, adding the bot token to OpenClaw configuration, and pairing Telegram accounts using pairing codes in the Gclaw chat interface. - [Connect Discord](https://gcore.com/docs/gclaw/connect-discord.md): Configure Gclaw Discord integration by creating a Discord bot application in the Developer Portal, enabling Message Content Intent, copying the bot token, adding it to OpenClaw configuration, and authorizing the bot to Discord servers with Read Messages/View Channels, Send Messages, and Read Message History permissions. - [Security model](https://gcore.com/docs/gclaw/security.md): Configure OpenClaw account isolation with dedicated VMs, unique API keys per account, and network isolation from Gcore backend; manage shared security responsibilities including prompt safety, credential protection, third-party bot token security, and agent activity monitoring. - [Limits and quotas](https://gcore.com/docs/gclaw/limits.md): Configure Gclaw inference limits including 200,000 token context window, 32,000 token maximum output, reasoning capability, and account-tier-dependent rate limits on Kimi-K2.5 model running on Gcore H200 GPUs. - [Pricing](https://gcore.com/docs/gclaw/pricing.md): Gclaw pricing includes Start plan at 35 EUR/month with dedicated OpenClaw instance and unlimited inference; beta access is free with single instance limit and no SLA commitments. - [SSH access to the Gclaw VM](https://gcore.com/docs/gclaw/ssh-access.md): Obtain SSH access to a Gclaw dedicated VM by generating an SSH key pair locally, asking the Gclaw assistant to append the public key to ~/.ssh/authorized_keys on the instance, retrieving the VM IP address with ip -4 a, and connecting as the ubuntu user. --- # Gcore Managed DNS > Manage DNS zones and records using Gcore Managed DNS with Anycast routing, geo-balancing, health checks, DNSSEC, and OctoDNS and Certbot plugin integration. - [Managed DNS](https://gcore.com/docs/dns.md): Manage DNS zones and records using Gcore Managed DNS with Anycast routing, geo-balancing, health checks, DNSSEC, and OctoDNS and Certbot plugin integration. - [GCore DNS overview](https://gcore.com/docs/dns/about-gcore-dns.md): Configure Managed DNS zones with authoritative DNS records, AnycastDNS routing, weight-based and geo-balancing, DNSSEC, Health Checks, CNAME flattening, HTTPS records, and IPv6 support via Gcore Customer Portal or API; use Public DNS resolvers for free recursive DNS resolution. - [GCore managed DNS glossary](https://gcore.com/docs/dns/gcore-dns-glossary.md): Define terminology for Gcore Managed DNS including A, AAAA, CNAME, MX, TXT, SRV records; DNS zones, DNS propagation, DNSSEC, authoritative name servers, and DNS queries. - [Getting started with managed DNS](https://gcore.com/docs/dns/manage-a-dns-zone.md): Create DNS zones in Gcore Managed DNS by specifying domain or subdomain names in the Customer Portal or API, updating NS records to Gcore nameservers, and managing zone records, TTL settings, and zone status through the All zones interface. ## Records - [Supported DNS record types](https://gcore.com/docs/dns/dns-records.md): Create A, AAAA, NS, CNAME, MX, TXT, SRV, SOA, CAA, TLSA, and PTR records in Gcore Managed DNS with TTL, class, and IPv4/IPv6 address values. - [Manage DNS records](https://gcore.com/docs/dns/dns-records/manage-dns-records-non-advanced-interface-mode.md): Create A, AAAA, NS, CNAME, MX, SRV, HTTPS, TXT, and CAA DNS records in Gcore Managed DNS zones via the Customer Portal by specifying record type, subdomain name, TTL in seconds, and record value. - [Manage DNS records (advanced interface mode with dynamic response)](https://gcore.com/docs/dns/dns-records/manage-dns-records-advanced-interface-mode-with-balancing.md): Create DNS record sets (RRSets) in Gcore Managed DNS advanced interface mode with support for A, AAAA, NS, CNAME, MX, SRV, HTTPS, TXT, CAA record types, configurable TTL, and dynamic response routing. - [Import and export records](https://gcore.com/docs/dns/dns-records/import-and-export-records.md): Export DNS records to BIND zone files (.zone format) containing domain name, TTL, RRset, refresh/update/expiry intervals, and authoritative NS servers, or import records from .zone files into Gcore Managed DNS zones. - [Create records in zone apex (CNAME flattening)](https://gcore.com/docs/dns/dns-records/specify-cname-at-root.md): Create CNAME records at zone apex using CNAME flattening in Gcore Managed DNS to resolve CNAME chains to final A or AAAA records, bypassing RFC 1034 restrictions that prevent CNAME coexistence with NS and SOA records. - [Configure DNS records to send emails](https://gcore.com/docs/dns/dns-records/set-up-dns-for-sending-email.md): Configure A, MX, PTR, and SPF TXT records in Gcore Managed DNS to enable email delivery, prevent spoofing, and block phishing via reverse DNS verification and Sender Policy Framework. - [Setting up a PTR record and reverse DNS zone](https://gcore.com/docs/dns/dns-records/set-up-a-ptr-record-and-reverse-dns-zone.md): Create PTR records in reverse DNS zones (in-addr.arpa for IPv4, ip6.arpa for IPv6) to map IP addresses to hostnames for anti-spam email authentication and subnet tracing via Gcore Managed DNS. - [What is an HTTPS record and how is it configured?](https://gcore.com/docs/dns/dns-records/what-is-an-https-record-and-how-is-it-configured.md): Create HTTPS records in Gcore Managed DNS to provide protocol versions, IPv4/IPv6 addresses, and alternate servers in a single DNS query, reducing connection round trips and TLS negotiation latency. ## Advanced managing - [Dynamic response](https://gcore.com/docs/dns/dns-records/configure-weight-balancing-and-geobalancing.md): Configure dynamic DNS responses using pickers (GeoDistance, Weighted shuffle, ASN, Country, Continent, Region, IP) and metadata to deliver different records based on user geolocation, autonomous system number, subnet, weight probability, or failover criteria in Gcore Managed DNS. - [What Healthcheck are and how to configure them](https://gcore.com/docs/dns/dns-failover/configure-and-use-dns-failover.md): Configure DNS Healthchecks to monitor server availability and exclude non-responding IPs from DNS responses, supporting round-robin and Geobalancing load distribution across multiple servers. - [Configure CDN integration](https://gcore.com/docs/dns/dns-records/advanced-managing/cdn-integration.md): Configure A/AAAA DNS records in Gcore Managed DNS zones to resolve directly to Gcore CDN addresses, eliminating CNAME configuration and enabling automatic routing to optimal CDN endpoints. - [Getting started with DNSSEC](https://gcore.com/docs/dns/getting-started-with-dnssec.md): Enable DNSSEC for Gcore Managed DNS zones to validate digital signatures across the chain of trust, obtain Delegation Signer (DS) records, and configure DS values in your domain registrar's control panel via API or portal. ## Integrations - [Use GCore managed DNS as a secondary DNS with OctoDNS](https://gcore.com/docs/dns/dns-plugins/use-gcore-dns-as-a-secondary-dns-with-octodns.md): Configure Gcore Managed DNS as secondary DNS using OctoDNS to synchronize DNS zones and records from primary DNS providers via Python virtual environment, pip package installation, and YAML configuration file with provider credentials. - [Get a Let's Encrypt certificate with Certbot](https://gcore.com/docs/dns/dns-plugins/get-a-let-s-encrypt-certificate-with-certbot.md): Configure Let's Encrypt certificate issuance with Certbot plugin using Gcore Managed DNS API credentials and DNS-01 challenge via TXT record automation on domains with Gcore nameservers ns1.gcorelabs.net and ns2.gcdn.services. ## Terraform - [Manage DNS zones and records via Terraform v0](https://gcore.com/docs/dns/dns-plugins/manage-dns-with-terraform.md): Create and manage Gcore Managed DNS zones and records using Terraform gcore_dns_zone and gcore_dns_zone_record resources, supporting A, AAAA, CNAME, MX, TXT, SRV, CAA record types, DNSSEC, SOA parameters, webhook notifications, and geo-balancing with continent and country blocks. - [Manage DNS zones and records via Terraform v2](https://gcore.com/docs/dns/dns-plugins/manage-dns-with-terraform-v2.md): Create and manage Gcore Managed DNS zones and records using Terraform provider v2 gcore_dns_zone and gcore_dns_zone_rrset resources, supporting A, AAAA, CNAME, MX, TXT, SRV, CAA, PTR record types, DNSSEC, SOA parameters, and geo-balancing with pickers and JSON-encoded meta values. --- # Gcore Hosting > Order and manage Gcore Dedicated Servers and Virtual Servers with DDoS protection, BGP, SSL certificates, account management, billing, and API-based server management. - [Hosting](https://gcore.com/docs/hosting.md): Order and manage Gcore Dedicated Servers and Virtual Servers with DDoS protection, BGP, SSL certificates, account management, billing, and API-based server management. ## Dedicated servers - [About dedicated server](https://gcore.com/docs/hosting/dedicated-servers/about-dedicated-servers.md): Deploy Gcore Dedicated Servers with Intel Xeon E3-1270 v5 processors, DDR4 ECC memory, IPMI management, and full OS installation capability for resource-intensive workloads, data storage, and non-virtualized applications. ## Before purchase - [Test the connectivity between your location and the server you want to buy](https://gcore.com/docs/hosting/virtual-servers/before-purchase/test-the-connectivity-between-your-location-and-the-server-you-want-to-buy.md): Use Gcore Looking Glass tool to test connectivity between your IP address and static nodes via ping, traceroute, BGP route queries, and autonomous system path analysis across multiple server locations. - [Order a dedicated server](https://gcore.com/docs/hosting/dedicated-servers/order-a-dedicated-server.md): Create a Dedicated Server order by selecting a tariff from the Control Panel or website, configuring parameters including domain name, operating system, included traffic, and additional IPv4/IPv6 addresses (up to 15 per server), then completing payment via available methods. - [Upgrade your dedicated server](https://gcore.com/docs/hosting/dedicated-servers/upgrade-your-dedicated-server.md): Upgrade Dedicated Server hardware specifications including RAID configuration, disk volume and count, RAM capacity, SSD/HDD type conversion, and 10 Gbps network cards via support ticket submission and paid service upgrade process. ## Manage - [Log in to DCImanager](https://gcore.com/docs/hosting/dedicated-servers/manage/log-in-to-dcimanager.md): Access DCImanager panel to manage dedicated servers, reboot, or stop servers using separate login credentials from the hosting control panel. - [Log in to IPMI](https://gcore.com/docs/hosting/dedicated-servers/manage/log-in-to-ipmi.md): Access IPMI interface for Dedicated Servers to remotely power on, power off, reboot servers, or reinstall OS via ISO through DCI manager or Gcore portal using local username and password authentication. ## Connect - [Connect to a Windows server](https://gcore.com/docs/hosting/dedicated-servers/manage/connect/connect-to-a-windows-server.md): Connect to Windows servers using Remote Desktop Connection with server IP address, username, and password credentials retrieved from the Gcore portal or purchase confirmation email. - [Connect to a Linux server](https://gcore.com/docs/hosting/dedicated-servers/manage/connect/connect-to-a-linux-server.md): Connect to Linux servers via SSH using server IP, username, and password, or access DCI Manager and VM Manager control panels with separate credentials. - [Manage SSH keys](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/manage-ssh-keys.md): Create and manage SSH public keys in Gcore Dedicated Servers portal by adding Key Name and Public Key fields; SSH keys automatically deploy to all future servers and OS reinstalls for authentication. - [Change the port for SSH connections](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/change-the-port-for-ssh-connections.md): Configure SSH port in sshd_config file by modifying the Port parameter, restarting the SSH service, and updating firewall rules to permit traffic on the new port. ## Operating system - [Install a Linux OS from your ISO image](https://gcore.com/docs/hosting/dedicated-servers/manage/operating-system/install-a-linux-os-from-your-iso-image.md): Deploy a Linux OS on a Dedicated Server by uploading a custom ISO image through the DCI manager, mounting it via IPMI Virtual Storage with Logical Drive type, and rebooting to begin installation. - [Install a Linux OS from a template](https://gcore.com/docs/hosting/dedicated-servers/manage/operating-system/install-a-linux-os-from-a-template.md): Install Linux OS templates including CentOS 7, Debian 8/10, FreeBSD 11/12, Ubuntu 16.04/18.04/20.04 on dedicated servers via DCI manager using the Install OS from template operation. ## Networking ## Additional IP addresses - [Buy an additional IP address](https://gcore.com/docs/hosting/dedicated-servers/manage/networking/additional-ip-addresses/buy-an-additional-ip-address.md): Purchase additional IPv4 and IPv6 addresses for Dedicated Servers and Virtual Private Servers via Control Panel, with limits of 14 IPv4 and 14 IPv6 addresses per server (2 IPv4 and 2 IPv6 for KVM-SSD-1 instances), and move additional IPs between servers through support. - [Configure an additional IP address](https://gcore.com/docs/hosting/virtual-servers/manage/networking/additional-ip-addresses/configure-an-additional-ip-address.md): Configure additional IP addresses on Virtual Private Servers and Dedicated Servers by editing network configuration files on Debian/Ubuntu, CentOS, or Windows Server 2012, specifying interface serial number, IPv4/IPv6 address, and netmask. - [Connect dedicated servers into a VLAN](https://gcore.com/docs/hosting/dedicated-servers/manage/networking/connect-dedicated-servers-into-a-vlan.md): Create VLANs for dedicated servers using DCI Manager to connect multiple servers into a virtual local network, adding VLAN members by selecting servers and network interfaces. - [Configure a 10 Gbps network card](https://gcore.com/docs/hosting/dedicated-servers/manage/networking/configure-a-10-gbps-network-card.md): Configure 10 Gbps network interfaces on Dedicated Servers by identifying active interfaces with ethtool, checking supported link modes, and activating 10 Gbps-capable network cards on Ubuntu/Debian using ip, ethtool, and nano configuration tools. - [Set up a PTR record](https://gcore.com/docs/hosting/virtual-servers/manage/set-up-a-ptr-record.md): Configure PTR records for virtual private servers and dedicated servers by mapping IP addresses to domain names to support email server identification and prevent spam filtering. - [Reboot a server](https://gcore.com/docs/hosting/dedicated-servers/manage/reboot-a-server.md): Reboot a dedicated server from the Control Panel or DCImanager. - [Check statistics of your dedicated server](https://gcore.com/docs/hosting/dedicated-servers/check-statistics-of-your-dedicated-server.md): Monitor incoming and outgoing traffic volume for dedicated servers in DCI Manager Statistics section using Traffic tab with customizable time period selection. - [Delete a dedicated server](https://gcore.com/docs/hosting/dedicated-servers/delete-a-dedicated-server.md): Delete a dedicated server via Control Panel to permanently remove the instance, erase all data, and stop billing charges. ## Troubleshooting - [Renew your server](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-a-server-that-was-suspended-for-non-payment.md): Recharge account balance or enable auto payment to renew suspended virtual servers; check payment status in Payments section and verify server activation after balance credit. - [Troubleshoot a server that is not responding to ping requests](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-a-server-that-is-not-responding-to-ping-requests.md): Troubleshoot ping connectivity issues by verifying IP address blocking via Great Firewall detection tools, checking network configuration settings including IP address, network mask, and default gateway in the control panel, and confirming additional IP addresses are configured on the server. - [Remove your IP address from blacklists](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/remove-your-ip-address-from-blacklists.md): Check if your IP address is blacklisted using third-party blacklist checking services, then contact the blacklist operator with details about your Gcore service usage to request delisting. - [Troubleshoot errors with ISO image installation](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-errors-with-iso-image-installation.md): Troubleshoot ISO image upload failures in Dedicated Servers - verify file naming uses lowercase .iso extension with alphanumeric characters only, confirm file size does not exceed 9 GB, and check account limit of 4 ISO images maximum. - [Troubleshoot IPMI errors](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-ipmi-errors.md): Diagnose IPMI login failures including autocomplete issues, error code 1006 (simultaneous sessions), IPMI URL unavailability, and remote console connection failures on Gcore Dedicated Servers via DCImanager. - [Troubleshoot issues with an incorrect IP location](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-issues-with-an-incorrect-ip-location.md): Verify IP geolocation accuracy using MaxMind and RIPE databases; contact Gcore support to submit location update requests to geolocation providers if IP location data is incorrect. - [Troubleshoot issues with SSH connection](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection failures by verifying port 22 availability using telnet or Putty, validating login credentials from Control Panel Instructions, and accessing VNC (VMmanager) or IPMI (DCImanager) for OS-level diagnostics on Virtual Private Servers and Dedicated Servers. - [Troubleshoot packet loss and high ping](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-packet-loss-or-high-ping.md): Diagnose packet loss and latency exceeding 110 milliseconds using ping, tracert, traceroute, and mtr commands; disable VPN/proxy and revert network settings to default parameters or contact support with server IP, client IP, geographic location, UTC timestamp, and bidirectional ping/traceroute output. ## Virtual servers - [About virtual servers](https://gcore.com/docs/hosting/virtual-servers/about-virtual-servers.md): Deploy KVM-based Virtual Servers on Debian, CentOS, Ubuntu, FreeBSD, Windows Server, or Solaris with guaranteed resource allocation, SSH access, VNC console, and SSD storage for isolated multi-tenant hosting. ## Before purchase - [Choose a virtual server for your needs](https://gcore.com/docs/hosting/virtual-servers/before-purchase/choose-a-virtual-server-for-your-needs.md): Compare Virtual Server plan categories KVM-SSD, KVM-SAS, KVM-HIGHCPU-SSD, and KVM-HIGHCPU-SAS by CPU cores, RAM, disk type (SSD or HDD SAS), data center location, and operating system availability to select appropriate billing plans. - [Test the connectivity between your location and the server you want to buy](https://gcore.com/docs/hosting/virtual-servers/before-purchase/test-the-connectivity-between-your-location-and-the-server-you-want-to-buy.md): Use Gcore Looking Glass tool to test connectivity between your IP address and static nodes via ping, traceroute, BGP route queries, and autonomous system path analysis across multiple server locations. - [Order a virtual server](https://gcore.com/docs/hosting/virtual-servers/order-a-virtual-server.md): Create a virtual server by selecting an OS, configuring additional IP addresses, specifying a domain name, and completing payment; server activation occurs within 3 hours and transitions through Ordered, Activation in progress, and Active statuses. - [Upgrade your virtual server](https://gcore.com/docs/hosting/virtual-servers/upgrade-your-virtual-server.md): Upgrade Virtual Server plan by selecting a new tariff with matching location and equal or higher vCPU, RAM, disk space, bandwidth, and traffic specifications, then submit a support ticket with server ID and desired plan for replacement within 30-60 minutes of downtime. ## Manage - [Features and functions of VMmanager 6](https://gcore.com/docs/hosting/virtual-servers/manage/main-features-and-functions-of-vmmanager-6.md): Manage virtual servers in VMmanager 6 control panel - start/stop/restart servers, reinstall OS via scripts, mount ISO images, change passwords, manage disks and backups, access VNC desktop, run bash/PowerShell scripts, view server statistics, and enable recovery mode with SystemRescueCD. ## Connect - [Connect to a Windows server](https://gcore.com/docs/hosting/dedicated-servers/manage/connect/connect-to-a-windows-server.md): Connect to Windows servers using Remote Desktop Connection with server IP address, username, and password credentials retrieved from the Gcore portal or purchase confirmation email. ## Linux server - [Connect to a Linux server via control panel](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/connect-to-a-linux-server-via-control-panel.md): Access Linux server console through VMmanager control panel using the monitor icon for remote server management. - [Connect to a Linux server via SSH](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/connect-to-linux-server-via-ssh.md): Connect to CentOS, Debian, Ubuntu, and FreeBSD servers via SSH protocol using username, server IP address, and password authentication from the portal Instructions tab. - [Manage SSH keys](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/manage-ssh-keys.md): Create and manage SSH public keys in Gcore Dedicated Servers portal by adding Key Name and Public Key fields; SSH keys automatically deploy to all future servers and OS reinstalls for authentication. - [Change the port for SSH connections](https://gcore.com/docs/hosting/virtual-servers/manage/connect/linux-server/change-the-port-for-ssh-connections.md): Configure SSH port in sshd_config file by modifying the Port parameter, restarting the SSH service, and updating firewall rules to permit traffic on the new port. - [Connect to a virtual server via VNC in VMmanager 6](https://gcore.com/docs/hosting/virtual-servers/manage/connect/connect-to-a-virtual-server-via-vnc.md): Connect to a virtual server via VNC console in VMmanager 6 using the Remote Frame Buffer protocol and root credentials from the Instructions tab. - [Install GUI (desktop environment) on Ubuntu, CentOS and Debian](https://gcore.com/docs/hosting/virtual-servers/manage/install-gui-desktop-environment-on-ubuntu-centos-and-debian.md): Install XFCE desktop environment on Ubuntu, CentOS, and Debian virtual servers via SSH or Control Panel using package managers and display managers like lightdm or gdm3. ## Operating system - [Buy a Windows server](https://gcore.com/docs/hosting/virtual-servers/manage/operating-system/buy-a-windows-server.md): Purchase a Windows Server VPS instance by selecting a data center, payment period (monthly, quarterly, semi-annual, annual), server plan (excluding KVM-SSD-1/2/3), and Windows Server operating system in the Gcore hosting control panel. - [Install a Linux OS from a template](https://gcore.com/docs/hosting/virtual-servers/manage/operating-system/install-a-linux-os-from-a-template.md): Reinstall Linux operating systems from templates including CentOS 7, Debian 8/10, FreeBSD 10/11/12, and Ubuntu 14.04/16.04/18.04/20.04 via VM Manager Control panel Reinstall button. - [Install a Linux OS from your ISO image](https://gcore.com/docs/hosting/virtual-servers/manage/operating-system/install-a-linux-os-from-your-iso-image.md): Deploy a Linux OS on a Gcore Virtual Server by attaching an ISO image, setting boot priority, and accessing the VM via VNC console. - [Install an operating system from a template in VMmanager 6](https://gcore.com/docs/hosting/virtual-servers/manage/operating-system/install-an-os-from-a-template-in-vmmanager-6.md): Deploy operating systems from templates in VMmanager 6 including CentOS 7, Debian 10/11, FreeBSD 12, Ubuntu 18.04/20.04/22.04 via Reinstall OS with optional application scripts and password configuration. - [Install OS from ISO on in VMmanager 6](https://gcore.com/docs/hosting/virtual-servers/manage/operating-system/install-an-os-from-iso-in-vmmanager-6.md): Mount ISO images to VMmanager 6 Virtual Servers via HTTP(S) or FTP URLs with maximum 8 GB file size, then install operating systems with optional OS tags for script execution. ## Networking - [Allocate an IPv6 address in VMmanager 6](https://gcore.com/docs/hosting/virtual-servers/manage/networking/allocate-an-ipv6-address-in-vmmanager-6.md): Allocate IPv6 subnets and addresses to Virtual Servers in VMmanager 6, with automatic assignment of the first subnet IP to the VM interface and manual OS-level configuration options. ## Additional IP addresses - [Buy an additional IP address](https://gcore.com/docs/hosting/dedicated-servers/manage/networking/additional-ip-addresses/buy-an-additional-ip-address.md): Purchase additional IPv4 and IPv6 addresses for Dedicated Servers and Virtual Private Servers via Control Panel, with limits of 14 IPv4 and 14 IPv6 addresses per server (2 IPv4 and 2 IPv6 for KVM-SSD-1 instances), and move additional IPs between servers through support. - [Configure an additional IP address](https://gcore.com/docs/hosting/virtual-servers/manage/networking/additional-ip-addresses/configure-an-additional-ip-address.md): Configure additional IP addresses on Virtual Private Servers and Dedicated Servers by editing network configuration files on Debian/Ubuntu, CentOS, or Windows Server 2012, specifying interface serial number, IPv4/IPv6 address, and netmask. - [Set up a PTR record](https://gcore.com/docs/hosting/virtual-servers/manage/set-up-a-ptr-record.md): Configure PTR records for virtual private servers and dedicated servers by mapping IP addresses to domain names to support email server identification and prevent spam filtering. - [Delete a virtual server](https://gcore.com/docs/hosting/virtual-servers/delete-a-virtual-server.md): Delete a virtual server from the Control Panel, which permanently erases all data and stops billing; deletion is blocked if the server was purchased less than one month ago due to minimum service term requirements. ## Troubleshooting - [Renew your server](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-a-server-that-was-suspended-for-non-payment.md): Recharge account balance or enable auto payment to renew suspended virtual servers; check payment status in Payments section and verify server activation after balance credit. - [Troubleshoot a server that is not responding to ping requests](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-a-server-that-is-not-responding-to-ping-requests.md): Troubleshoot ping connectivity issues by verifying IP address blocking via Great Firewall detection tools, checking network configuration settings including IP address, network mask, and default gateway in the control panel, and confirming additional IP addresses are configured on the server. - [Remove your IP address from blacklists](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/remove-your-ip-address-from-blacklists.md): Check if your IP address is blacklisted using third-party blacklist checking services, then contact the blacklist operator with details about your Gcore service usage to request delisting. - [Troubleshoot errors with ISO image installation](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-errors-with-iso-image-installation.md): Troubleshoot ISO image upload failures in Virtual Servers - verify lowercase .iso file extension, alphanumeric filename, file size under 8 GB, and account limit of 3 ISO images per account. - [Troubleshoot blocked SMTP ports](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-blocked-smtp-ports.md): Troubleshoot blocked SMTP ports 25, 465, and 587 on Virtual Servers by checking Support tickets for spam-related blocks, verifying compliance with Acceptable Use Policy, and contacting technical support with domain name or server configuration details to request port unblocking. - [Troubleshoot issues with an incorrect IP location](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-issues-with-an-incorrect-ip-location.md): Verify IP geolocation accuracy using MaxMind and RIPE databases; contact Gcore support to submit location update requests to geolocation providers if IP location data is incorrect. - [Troubleshoot issues with SSH connection](https://gcore.com/docs/hosting/virtual-servers/troubleshooting/troubleshoot-issues-with-ssh-connection.md): Troubleshoot SSH connection failures by verifying port 22 availability using telnet or Putty, validating login credentials from Control Panel Instructions, and accessing VNC (VMmanager) or IPMI (DCImanager) for OS-level diagnostics on Virtual Private Servers and Dedicated Servers. - [Troubleshoot packet loss and high ping](https://gcore.com/docs/hosting/dedicated-servers/troubleshooting/troubleshoot-packet-loss-or-high-ping.md): Diagnose packet loss and latency exceeding 110 milliseconds using ping, tracert, traceroute, and mtr commands; disable VPN/proxy and revert network settings to default parameters or contact support with server IP, client IP, geographic location, UTC timestamp, and bidirectional ping/traceroute output. ## Other services ## DDoS protection - [About GCore DDoS protection for dedicated servers](https://gcore.com/docs/hosting/other-services/ddos-protection/about-gcore-ddos-protection-for-dedicated-servers.md): Configure Gcore DDoS Protection for Dedicated Servers using Basic (free) or Advanced (paid) always-on mode with traffic redirection through Threat Mitigation System (TMS) to filter amplification attacks, volumetric attacks (L3), connection attacks (L4), and application layer attacks (L5-L7) with configurable ACL and OSI layer protection ranges (L3-L4 or L3-L7). - [Activate DDoS protection for your dedicated servers](https://gcore.com/docs/hosting/other-services/ddos-protection/activate-ddos-protection-for-your-dedicated-servers.md): Activate DDoS protection for dedicated servers by specifying OSI layers (L3-L4 or L3-L7), bandwidth, and optional IP whitelist/blacklist; protection applies to rented Gcore servers, third-party servers, or new server orders. ## DNS hosting - [Manage DNS hosting](https://gcore.com/docs/hosting/other-services/dns-hosting/manage-dns-hosting.md): Activate and configure Gcore DNS hosting service to manage DNS records for up to 25 domains, setting administrator email, name servers, mail servers (MX records), and subdomains (A records) via the control panel. ## SSL certificates - [About SSL certificates](https://gcore.com/docs/hosting/other-services/ssl-certificates/about-ssl-certificates.md): Configure domain-validated (DV) and company-validated (OV) SSL certificates including RapidSSL, Comodo Positive SSL, Comodo Essential SSL, Thawte SSL123, and Wildcard variants to encrypt communications and protect sensitive data on subdomains. - [Activate an SSL certificate](https://gcore.com/docs/hosting/other-services/ssl-certificates/activate-an-ssl-certificate.md): Activate DV and OV SSL certificates via email confirmation link or company verification process through certification authority audit. ## BGP - [Activate BGP](https://gcore.com/docs/hosting/other-services/bgp/activate-bgp.md): Enable BGP service on Dedicated Servers to announce custom IP addresses via Border Gateway Protocol, available through Control Panel ordering and technical support configuration. ## Link aggreagtion - [Activate Link aggregation](https://gcore.com/docs/hosting/other-services/link-aggreagtion/activate-link-aggregation.md): Configure Link Aggregation Control Protocol (LACP) bonding on Gcore Bare Metal servers using Port Channel service, ifenslave package, bonding kernel module, and network interface configuration to aggregate multiple Ethernet channels for load balancing and fault tolerance. ## Account management - [Set up notifications](https://gcore.com/docs/hosting/account-management/set-up-notifications.md): Configure email notifications in Control Panel User Settings to receive alerts for server end dates and support ticket responses. - [Manage your password](https://gcore.com/docs/hosting/account-management/manage-your-password.md): Change or recover Control Panel password via Client Profile section or password recovery page; password must contain minimum 8 characters including uppercase letter and number; account temporarily disabled after 3 failed login attempts. - [Set up two-factor authentication](https://gcore.com/docs/hosting/account-management/set-up-two-factor-authentication.md): Enable two-factor authentication in user Settings using Google Authenticator app to scan QR code or manual key entry, then verify with six-digit codes during login and disable via Settings when needed. ## Users - [Add a new user to your account](https://gcore.com/docs/hosting/account-management/users/add-a-new-user-to-your-account.md): Create new Control Panel user accounts with name, email, and password via Tools menu; manage user list and credentials in Client section. - [Configure user rights](https://gcore.com/docs/hosting/account-management/users/configure-user-rights.md): Configure user rights in Control Panel by enabling or disabling access to sections, subsections, and operations per user via Perm settings, or grant Full access permissions to bypass restrictions. - [View the authorization history of your account](https://gcore.com/docs/hosting/account-management/view-the-authorization-history-of-your-account.md): View account authorization history including login timestamps, user email and ID, and source IP addresses in Control Panel Statistic Access Log. ## Payments - [Pay for GCore services (payment methods)](https://gcore.com/docs/hosting/payments/pay-for-gcore-services-payment-methods.md): Configure account payments in USD or EUR via PayPal, bank transfer, bank card (Visa, MasterCard, American Express, Union Pay), or Alipay through Dashboard Add funds interface with payer selection and company details. - [Renew the server](https://gcore.com/docs/hosting/payments/renew-your-server.md): Enable auto-renewal for Virtual Servers and Dedicated Servers by maintaining account balance; servers suspend after insufficient funds and delete after 1 or 14 days depending on plan type (KVM-SSD-1, KVM-SAS-1, or other plans), with automatic reactivation within 5 minutes upon payment. - [Set up auto payment](https://gcore.com/docs/hosting/payments/set-up-auto-payment.md): Enable auto payment with configurable monthly charge-off limits to automatically recharge account balance from bank card when funds are insufficient for service renewal; auto payment does not cover traffic overcommitment charges. - [Troubleshoot payment errors](https://gcore.com/docs/hosting/payments/troubleshoot-payment-errors.md): Troubleshoot payment errors for PayPal, bank cards, AMEX, WeChat, AliPay, and bank transfers including insufficient funds, declined transactions, unsupported currency-provider combinations, and Ayden processing failures. - [Check the payment history](https://gcore.com/docs/hosting/payments/check-the-payment-history.md): View payment history and invoices in Gcore Control Panel Billing section; print or download invoices as PDF files for each transaction. - [Request a refund](https://gcore.com/docs/hosting/payments/request-a-refund.md): Request refunds to account balance via Control Panel support ticket, providing refund reason and server details; refunds processed Monday to Friday. - [Contact our technical support](https://gcore.com/docs/hosting/contact-our-technical-support.md): Contact Gcore technical support via 24/7 live chat on the website or by submitting support tickets through the Control Panel Support Tickets section. - [Manage hosting services via API](https://gcore.com/docs/hosting/manage-hosting-services-via-api.md): Manage hosting services via Billmanager API for server provisioning and payments, DCImanager API for Dedicated Server management, and VMmanager API for VPS management. - [Become a reseller and resell our services](https://gcore.com/docs/hosting/become-reseller-and-resell-our-services.md): Contact Gcore technical support to apply for reseller partnership program, specify company name, user count, product type (VPS or dedicated server), and expected sales volume to receive reseller discounts in Control Panel. --- # Gcore Object Storage > Store and manage data in Gcore S3-compatible Object Storage with S3 Fast (high-performance AI/ML workloads), S3 Standard (general-purpose backups), and SFTP storage types. - [Object Storage](https://gcore.com/docs/storage.md): Store and manage data in Gcore S3-compatible Object Storage with S3 Fast (high-performance AI/ML workloads), S3 Standard (general-purpose backups), and SFTP storage types. - [How storage is billed](https://gcore.com/docs/storage/how-storage-is-billed.md): Configure billing for Gcore Object Storage S3 Standard, S3 Fast, and SFTP storage types with per-GB/month storage rates, egress/ingress charges, request pricing, and self-commit discount plans; manage plan changes and subscription fees charged monthly on the 2nd day. - [Create an object or SFTP storage](https://gcore.com/docs/storage/create-an-s3-or-sftp-storage.md): Create S3 Standard, S3 Fast, or SFTP storage in Gcore Object Storage with access keys, SSH keys, or password authentication; configure server alias, Expires header, and manage up to 3600 storages per account with maximum 1000 buckets per storage and 10 million objects per bucket. - [Use storage as the origin for your CDN resource](https://gcore.com/docs/storage/use-storage-as-the-origin-for-your-cdn-resource.md): Configure Gcore CDN resources with Object Storage or SFTP storage as origins using bucket paths, storage hostnames, custom domains, and authentication options for public or private buckets. ## Manage object storage - [Managing buckets through the customer portal](https://gcore.com/docs/storage/manage-object-storage/manage-buckets-via-the-control-panel.md): Create S3 buckets in Gcore Object Storage with naming constraints (3-63 characters, lowercase, no underscores or consecutive dots), configure CORS policy per bucket, and manage file uploads via the customer portal file manager using Access Key and Secret Key authentication. ## Configure AWS CLI, S3cmd, and AWS JavaScript SDK - [Connect AWS CLI, S3cmd, and AWS JavaScript SDK](https://gcore.com/docs/storage/manage-object-storage/configure-aws-sli-s3cmd-and-aws-javascript-sdk/connect-aws-cli-s3cmd-and-aws-sdk.md): Configure AWS CLI and S3cmd to access Gcore Object Storage using S3-compatible credentials - Access Key, Secret Key, and storage region endpoint via aws configure and s3cmd --configure commands. - [Remove objects from a bucket automatically with AWS CLI](https://gcore.com/docs/storage/manage-object-storage/configure-aws-sli-s3cmd-and-aws-javascript-sdk/remove-objects-from-a-bucket-automatically-with-aws-cli.md): Configure lifecycle policies in Gcore Object Storage buckets using AWS CLI to automatically expire and remove objects based on age, with XML rule definitions specifying expiration days, object prefixes, and enabled status. - [Configure access control on S3 storage with AWS CLI and S3cmd](https://gcore.com/docs/storage/manage-object-storage/configure-aws-sli-s3cmd-and-aws-javascript-sdk/configure-access-control-on-s3-storage-with-aws-cli-and-s3cmd.md): Configure Object Storage access control using AWS CLI and S3cmd with ACLs (--public-read, --private, --grant-full-control, --grant-read, --grant-write) and JSON policies to manage permissions for buckets and objects in Gcore Object Storage. - [Generate temporary links to files with AWS CLI and S3cmd](https://gcore.com/docs/storage/manage-object-storage/configure-aws-sli-s3cmd-and-aws-javascript-sdk/generate-temporary-links-to-files-with-aws-cli-and-s3cmd.md): Generate presigned URLs for temporary S3 Object Storage file access using AWS CLI with bucket name, object key, expiration duration in seconds, and storage hostname, or S3cmd with bucket name, object key, and Unix timestamp expiry. - [S3 service URLs and default region names](https://gcore.com/docs/storage/manage-object-storage/s3-service-urls-and-default-region-names.md): Configure S3-compatible clients with Gcore Object Storage service URLs and default region names for S3 Fast (sines-2, sines-3, london-2) and S3 Standard (luxembourg-2, chicago-1) locations using endpoints like sines-2.storage.gcore.dev and region parameters like s-ndp1-2. ## Manage SFTP storage - [Connect to your storage with FileZilla](https://gcore.com/docs/storage/manage-sftp-storage/connect-to-your-storage-with-filezilla.md): Configure FileZilla SFTP connection to Gcore Storage using SSH File Transfer Protocol on port 2200 with password or SSH key authentication. - [Create and add an SSH key to your storage](https://gcore.com/docs/storage/manage-sftp-storage/create-and-add-an-ssh-key-to-your-storage.md): Create and assign SSH keys for SFTP storages by uploading public key text or files, naming keys with alphanumeric characters and underscores up to 128 symbols, and linking keys to storage resources via the SSH keys manager. - [Request content directly from the storage](https://gcore.com/docs/storage/request-content-directly-from-the-storage.md): Request content directly from object storage and SFTP storage using HTTP/HTTPS protocols with bucket hostname and file path schema. - [Check storages usage reports](https://gcore.com/docs/storage/check-storages-usage-reports.md): View storage usage reports in Statistics section with metrics for used space, requests, and traffic; filter by time period (day, week, month, year, custom), storage type (Object Storage, SFTP Storage), location, and name; data aggregates hourly max and average values. - [4xx errors: how to solve storage issues](https://gcore.com/docs/storage/4xx-errors-how-to-solve-storage-issues.md): Resolve HTTP 404 and HTTP 403 errors when requesting content from Gcore Object Storage or SFTP storage by verifying file uploads, using correct regional URLs, and configuring bucket and file ACL rules for public access via AWS CLI or s3cmd. --- # Gcore Video Streaming > Gcore Video Streaming is a high-load video streaming PaaS. Scale to 1M+ viewers and beyond - [Gcore Video Streaming](https://gcore.com/docs/streaming.md): Gcore Video Streaming is a high-load video streaming PaaS. Scale to 1M+ viewers and beyond ## AI video services - [AI video services](https://gcore.com/docs/streaming/video-hosting/ai-video-service.md): Configure AI video services for Video Streaming including AI ASR subtitle generation and translation, content moderation tasks (nsfw, soft_nudity, sports, weapons detection), and API integration for VOD and live streaming workflows. ## Content moderation - [Content moderation](https://gcore.com/docs/streaming/ai-video-service/content-moderation.md): Detect NSFW materials, hard nudity, soft nudity, and sport activities in video and image content using Gcore AI content moderation with real-time keyframe analysis and configurable probability thresholds for age-appropriate filtering. - [Not safe for work (NSFW) detection](https://gcore.com/docs/streaming/ai-video-service/content-moderation/nsfw-detection.md): Configure NSFW detection in Gcore Streaming AI to identify and filter inappropriate workplace content in MP4 videos via the Customer Portal, specifying Origin URL or uploaded video source, selecting Content moderation task type, and receiving confidence scores for detected sensitive material. - [Hard nudity detection](https://gcore.com/docs/streaming/ai-video-service/ai-nudity-detection.md): Configure hard nudity detection in Gcore Streaming AI to identify explicit nudity involving genitals in MP4 videos via portal task creation, returning confidence scores and detected body part locations by frame number. - [Soft nudity detection](https://gcore.com/docs/streaming/ai-video-service/content-moderation/soft-nudity-detection.md): Configure soft nudity detection in Gcore Streaming AI to identify explicit and partial nudity including male and female faces and uncovered body parts in MP4 videos via the portal, with detection results including object type, frame number, and confidence probability threshold of 30%. - [Sport detection](https://gcore.com/docs/streaming/ai-video-service/content-moderation/sport-detection.md): Configure sport detection content moderation tasks in Gcore Streaming AI to identify sporting activities, actions, and events in MP4 videos via portal or API, returning detected objects with frame numbers and confidence probability scores above 30%. ## Generate and translate captions - [Generate and translate captions](https://gcore.com/docs/streaming/video-hosting/ai-for-video/generate-ai-subtitles-and-add-them-to-video.md): Generate video captions and subtitles using Gcore AI automated speech recognition (ASR) with Whisper models to transcribe audio in 100+ languages and translate captions for multilingual audiences via Customer Portal or API. - [Generate and translate AI captions in the customer portal](https://gcore.com/docs/streaming/ai-video-service/generate-ai-subtitles-and-add-them-to-video/generate-captions-in-customer-portal.md): Create AI caption generation and translation tasks in Gcore Streaming portal by specifying Origin URL (external HTTP/HTTPS MP4 or hosted video), selecting Transcribe & Translate Captions task type, configuring Audio language (Auto-detect or manual), and Subtitles language for transcription or multi-language translation. - [Generate and translate AI captions for VOD](https://gcore.com/docs/streaming/ai-video-service/generate-ai-subtitles-and-add-them-to-video/generate-captions-via-api.md): Generate AI captions and translate subtitles for VOD videos in Gcore Video Streaming using transcribe and translate parameters in video upload or subtitle post-processing APIs, or process external MP4 files via direct HTTPS links with the native AI API. - [Streaming usage and billing metrics](https://gcore.com/docs/streaming/how-the-streaming-platform-and-additional-features-are-billed.md): Configure Gcore Streaming Platform billing with committed volume tariff plans, PAYG usage-based pricing, and default storage limits of 100,000 minutes for video assets; track transcoding, storage, CDN delivery, and AI services consumption via billing reports and usage metrics. ## Codecs and protocols - [Accepted input parameters for live streams and videos](https://gcore.com/docs/streaming/live-streams-and-videos-protocols-and-codecs/input-parameters-and-codecs.md): Configure live stream input parameters including ingest protocols (RTMP, RTMPS, SRT, RTSP, HLS PULL, WebRTC), video codec (H.264), audio codec (AAC), frame rate (up to 60 fps), keyframe interval (1-2 seconds), bitrate mode (CBR), chroma subsampling (4 -2 -0), and audio sample rate (44.1 or 48 kHz) for Gcore Streaming transcoding; upload VOD files up to 30 GB with consistent codec, resolution, and frame rate parameters to avoid transcoding errors. - [Output parameters after transcoding: codecs, bitrate, frame rate](https://gcore.com/docs/streaming/live-streams-and-videos-protocols-and-codecs/output-parameters-and-codecs.md): Configure HLS MPEG-TS, HLS CMAF, MPEG-DASH, and MP4 output protocols for Gcore Video Streaming with codec support (H.264, HEVC, AV1, VP9), segment formats (MPEG-TS, fragmented MP4, WebM), and adaptive bitrate transcoding for Live and VOD delivery. - [RTMP](https://gcore.com/docs/streaming/live-streaming/protocols/rtmp.md): Configure RTMP and RTMPS ingest for live streaming encoders using server URLs, stream keys, and H.264 video plus AAC audio codec on ports 1935 (RTMP/TCP) and 443 (RTMPS/TCP). - [SRT](https://gcore.com/docs/streaming/live-streaming/protocols/srt.md): Configure SRT (Secure Reliable Transport) UDP-based protocol for live streaming ingestion with encoder settings including video codec, bitrate, latency window, keyframe interval, CPU preset, profile, tune, and x264/x265 options; obtain ingest URLs with server location, port 5001, stream key, and backup URL via portal or API; configure optional passphrase protection via API for SRT PUSH workflows. - [WebRTC WHIP to HLS/DASH](https://gcore.com/docs/streaming/live-streaming/protocols/webrtc.md): Convert WebRTC WHIP ingest streams to HLS/DASH playback using Gcore Video Streaming platform with H.264 video and OPUS audio encoding, adaptive bitrate streaming, and regional WHIP servers for low-latency browser-based ingestion. - [RTMP vs SRT: protocol comparison](https://gcore.com/docs/streaming/live-streaming/protocols/rtmp-srt.md): Compare RTMP (TCP-based) and SRT (UDP-based) streaming protocols for packet loss, jitter, latency, bandwidth limitations, and encoder buffering behavior on unstable networks. ## Player - [Built-in web player](https://gcore.com/docs/streaming/player/customize-appearance-of-the-built-in-player.md): Embed HTML5 video player via iframe with customization options for branding, colors, logo, autoplay, mute, playback speed controls, and view statistics for VOD and Live streams. - [JS Video Player & SDK](https://gcore.com/docs/streaming/player/player-api-tutorial.md): Configure Gcore JS Video Player (@gcorevideo/player) to support HLS, LL-HLS, MPEG-DASH, LL-DASH, and MP4 playback with low-latency adaptive streaming, plugins, SDK methods, events, and error handling via hls.js, dash.js, and native video element. ## Extra features - [Video streaming API tutorial](https://gcore.com/docs/streaming/api/streaming-platform-api-tutorial.md): Create streams and broadcasts using Video Streaming API endpoints post_streams_id and post_broadcasts, activate streams with patch_streams_id, update broadcast status to live with patch_broadcasts_id, and handle webhooks with live status notifications for video streaming integration. - [Webhooks on system state changes](https://gcore.com/docs/streaming/extra-features/get-webhooks-from-the-streaming-platform.md): Configure webhooks for Video Streaming system state changes on Live streams, VOD videos, VOD deletes, and Restreamings entities via HTTP POST callbacks with payload fields including stream id, live status, backup_live, recording, transcoding readiness, pull origin type, uri, and stream_source_type. ## Interaction with CDN - [Get started with CDN for video streaming](https://gcore.com/docs/streaming/interaction-with-cdn/get-started-streaming-cdn.md): Configure automatic CDN delivery for video streaming with integrated caching at 210+ edge locations, adaptive bitrate delivery, and per-minute billing based on total content minutes delivered to viewers. - [Use custom CDN resources with video streaming](https://gcore.com/docs/streaming/interaction-with-cdn/custom-cdn-resource.md): Create dedicated custom CDN resources for Video Streaming with advanced security policies including geo-blocking, referrer validation, IP allowlists/blocklists, custom domains, secure tokens, and granular caching control billed per-GB instead of per-minute. - [Protect content with video secure tokens](https://gcore.com/docs/streaming/interaction-with-cdn/video-secure-token.md): Configure video secure tokens to restrict content access by user authentication, expiration time, and per-user token generation for paid subscriptions, private videos, time-limited previews, and anti-hotlinking protection. - [Auto-refresh video secure tokens](https://gcore.com/docs/streaming/interaction-with-cdn/token-auto-refresh.md): Configure auto-refresh video secure tokens with short TTL (60 seconds) and IP-bound mode to prevent link sharing in HLS/DASH streams; refresh tokens automatically in the player before expiry to invalidate copied URLs while maintaining uninterrupted playback. ## Live streaming - [Getting started with live streaming](https://gcore.com/docs/streaming/live-streaming/getting-started-with-live-streaming.md): Learn what Gcore Live Streaming provides for live video workflows - RTMP, SRT, and WebRTC WHIP ingest, adaptive bitrate HLS/DASH delivery, low-latency modes, overlays, playlists, live clipping, restreams, recording, and DVR features. - [Create and manage a live stream](https://gcore.com/docs/streaming/live-streaming/create-a-live-stream.md): Configure live video streaming with RTMP, SRT, or WebRTC WHIP ingest protocols, transcode to adaptive bitrate HLS/DASH delivery in low-latency (LL-HLS, LL-DASH) or standard modes, and enable overlays, playlists, live clipping, restreams, recording, and DVR features via Gcore Live Streaming portal. ## Broadcasting software - [FFmpeg](https://gcore.com/docs/streaming/live-streaming/broadcasting-software/ffmpeg.md): Configure FFmpeg command-line parameters for RTMP live streaming to Gcore Video Streaming, including video bitrate (2000Kbps for 720p, 4000Kbps for 1080p), audio bitrate (128Kbps), H.264 encoder, keyframe interval (2s), CPU preset (veryfast), and resolution downscaling via bicubic filter. - [GStreamer](https://gcore.com/docs/streaming/live-streaming/broadcasting-software/gstreamer.md): Configure GStreamer pipelines with videotestsrc, audiotestsrc, x264enc, and container multiplexers (FLV, MPEG-TS) to encode and push live streams to Gcore RTMP or SRT ingest endpoints using H.264 video, AAC audio, and protocol-specific sink elements (rtmpsink, srtsink). - [Larix](https://gcore.com/docs/streaming/live-streaming/broadcasting-software/larix.md): Configure Larix mobile encoder to stream to Gcore Video Streaming via RTMP URL and stream key, using Larix Grove to generate QR code configurations with camera resolution, frame rate, video bitrate, keyframe interval, and audio bitrate parameters. - [Open Broadcaster Software](https://gcore.com/docs/streaming/live-streaming/broadcasting-software/obs.md): Configure OBS encoder settings for Gcore Video Streaming by entering RTMP Server URL and Stream Key from Live stream settings, then adjust Video Bitrate (2000Kbps for 720p, 4000Kbps for 1080p), Audio Bitrate (128), and Encoder parameters in Output, Audio, and Video tabs. - [Instant clips](https://gcore.com/docs/streaming/live-streaming/clips.md): Create instant clips from ongoing live streams in HLS (.m3u8) or MP4 formats with configurable expiration (1 minute to 4 hours), stored in server memory until expiration or conversion to permanent VOD. - [Pause and rewind the live streams](https://gcore.com/docs/streaming/live-streaming/pause-and-rewind-the-live-streams.md): Enable DVR (Digital Video Recorder) feature on live streams to cache and allow viewers to pause and rewind broadcasts within a 1-hour window by default, configurable up to 4 hours via API PATCH /streaming/streams/{id} with dvr-duration parameter. - [How low-latency streaming works](https://gcore.com/docs/streaming/live-streaming/how-low-latency-streaming-works.md): Configure low-latency live streaming with LL-HLS and LL-DASH protocols using CMAF and fMP4 containers to achieve 2–5 seconds latency; ingest RTMP or SRT streams, transcode to adaptive bitrate, and deliver via CDN with manifest blocking and chunked downloads. - [Combine multiple live streams](https://gcore.com/docs/streaming/live-streaming/combine-multiple-live-streams.md): Configure Multicamera to combine multiple live streams into a single player with stream status selection, custom player assignment, stream ordering, and screensaver upload for multi-angle or multi-language broadcasts. - [Insert an overlay (HTML widgets) in your live stream](https://gcore.com/docs/streaming/live-streaming/insert-html-overlays-in-live-streams.md): Configure HTML overlays embedded into live streams via API with support for multiple overlays per stream, transparent areas, 1 FPS update frequency, automatic scaling across adaptive bitrate qualities, and positioning in any screen area. - [Understanding of PTS and DTS in RTMP/SRT master streams](https://gcore.com/docs/streaming/live-streaming/pts-dts.md): Configure PTS (Presentation Timestamp) and DTS (Decoding Timestamp) in RTMP and SRT master streams to ensure monotonic, non-gapped frame timelines; incorrect timestamps cause decoder frame drops, segment misalignment in HLS/DASH, audio/video desynchronization, and transcoder failures in Gcore Cloud. - [Primary, Backup, and Global Ingest Points for PUSH and PULL](https://gcore.com/docs/streaming/live-streaming/primary-backup.md): Configure PUSH and PULL ingest points for Gcore Streaming Platform using RTMP, RTMPS, SRT, or WebRTC WHIP protocols with stream keys and push tokens for live video ingestion from encoders or origin servers. - [Record your live streams and save them as videos](https://gcore.com/docs/streaming/live-streaming/record-your-live-streams-and-save-them-as-videos.md): Enable manual or automatic recording of live streams via Gcore Streaming portal or API using the record feature to save stream fragments or entire sessions to Streaming Storage, with automatic splitting for interruptions over one minute and recordings exceeding four hours. - [Create and configure a restream](https://gcore.com/docs/streaming/live-streaming/create-and-configure-a-restream-to-social-media.md): Broadcast live streams to multiple social media platforms (YouTube, Facebook, Twitch) via RTMP/RTMPS restreaming by configuring credentials and selecting tar... ## Q&A and Case studies - [Streaming FAQs](https://gcore.com/docs/streaming/faq/streaming-faq.md): Configure Gcore Video Streaming for live and on-demand delivery with LL-HLS, LL-DASH, HLS MPEG-TS, CMAF, and MP4 protocols; manage transcoding up to Full HD, CDN billing per minute or GB, storage for VOD and recorded streams, and usage estimation via pricing calculator. - [Case Study: Mastering 24/7 Live Streaming with Hot-Swapping](https://gcore.com/docs/streaming/faq/case-study-hot-swapping-elemental.md): Configure 24/7 live streaming with hot-swapping between primary and backup encoders using AWS Elemental Live, Nimble Streamer SRT gateway, and Gcore Video Streaming Global Ingest points; implement cross-pull redundancy via SRT protocol to prevent head-of-line blocking and maintain absolute timing synchronization during encoder failover. - [Video streaming HTTP status codes](https://gcore.com/docs/streaming/faq/http-status-codes.md): Reference HTTP status codes 200, 403, 404, 422, 500, 502, 503, 504 returned by Gcore Video Streaming API when requesting manifests (.m3u8, .mpd) and chunks (.ts, .mp4), including geo-restriction, token authentication, CMAF format X-Err-Code headers, and transcoding error diagnostics. - [Live Streaming issues](https://gcore.com/docs/streaming/faq/live-streaming-issues.md): Troubleshoot Live Streaming issues including DVR chunk retention, low-latency HLS buffering, empty manifests, packet loss via SRT, and restream failures by checking encoder settings, bitrate stability, key frame intervals, network latency, and manifest generation. - [VOD issues](https://gcore.com/docs/streaming/faq/vod-issues.md): Troubleshoot VOD upload failures, transcoding errors, and playback issues including 503 errors, interrupted uploads, session timeouts, processing queue delays, inconsistent video parameters causing Error status, HTTP 404 responses, and high segment latency or TTFB. ## WebRTC issues - [Fix the camera or microphone if they do not work](https://gcore.com/docs/streaming/faq/real-time-video-issues/fix-the-camera-or-microphone-if-they-do-not-work.md): Troubleshoot camera and microphone failures in video calls by verifying browser version compatibility (Chrome 70+, Firefox 70+, Safari 12+, Edge 79+, Opera 60+) and enabling Camera and Microphone permissions in browser settings for Chrome, Firefox, and other supported browsers. - [Audio quality is reduced when using bluetooth headsets in video call apps](https://gcore.com/docs/streaming/faq/real-time-video-issues/audio-quality-is-reduced-when-using-bluetooth-headsets-in-video-call-apps.md): Troubleshoot Bluetooth audio quality degradation in video call applications caused by profile switching from A2DP (Advanced Audio Distribution Profile) to HSP/HFP (Headset Profile/Hands-Free Profile) when microphone input is required. ## Statistics - [Video player metrics](https://gcore.com/docs/streaming/statistics/statistics-of-built-in-player.md): Monitor Video Hosting player metrics including average view duration, viewer geography, browsers, operating systems, hosts, and viewer count via the Player metrics tab in Gcore Customer Portal with UTC or local timezone filtering and auto-refresh intervals. - [Video views and delivered minutes](https://gcore.com/docs/streaming/statistics/statistics-of-views.md): Monitor video views and delivered minutes through Gcore Video Hosting Statistics tab in the Customer Portal, tracking unique viewers counted once per session and total CDN delivery minutes by time period filters. - [View your live stream metrics](https://gcore.com/docs/streaming/statistics/view-your-live-stream-metrics.md): Monitor live stream performance metrics including video bitrate, FPS, and key frame interval via Live Stream Monitoring in Gcore Streaming platform, with 1-minute resolution data stored for one year. - [View statistics of live streams and videos](https://gcore.com/docs/streaming/statistics/view-statistics-of-live-streams-videos-and-billing.md): View statistics for videos and live streams in Gcore Streaming via Reports page, filtering by Viewers, Browsers, OS, Geography, Hosts, and Popular videos parameters with configurable time intervals and date ranges. ## Video hosting - [Getting started with video hosting](https://gcore.com/docs/streaming/video-hosting/getting-started-with-video-hosting.md): Start using Gcore Video Hosting for video-on-demand workflows - upload and transcode videos, deliver HLS, MPEG-DASH, and MP4 playback through the Gcore player or your own player, organize a VOD library, add subtitles and multiple audio tracks, protect videos, and analyze viewer engagement. ## Manage library - [Upload a video and embed it into your app](https://gcore.com/docs/streaming/video-hosting/upload-a-video-and-embed-it-to-your-app.md): Configure Gcore Video Hosting to upload videos via direct upload, Google Drive import, TUS protocol resumable uploads, or remote URL fetch, then deliver adaptive bitrate HLS MPEG-TS, HLS CMAF, MPEG-DASH CMAF, MP4, HEVC, AV1, VP9, and 8K resolution renditions with multi-audio tracks, subtitles, custom thumbnails, and analytics. - [Organize uploaded videos](https://gcore.com/docs/streaming/video-hosting/organize-uploaded-videos.md): Organize videos in Gcore Streaming using directories and tags for filtering and grouping by metadata; create directories, upload videos, move videos between directories, add tags to videos, and filter videos by tag names in the Customer Portal. - [Delete uploaded videos](https://gcore.com/docs/streaming/video-hosting/delete-videos.md): Delete uploaded videos from Gcore Video Hosting via Customer Portal or DELETE /videos API endpoint; permanently removes all transcoded versions, subtitles, screenshots, and associated data from cloud storage. - [Download files](https://gcore.com/docs/streaming/video-hosting/original-files.md): Download transcoded video files in multiple codecs and resolutions from Gcore Video Streaming via Customer Portal after original files are deleted post-transcoding. - [Protect your videos with the AES-128 encryption](https://gcore.com/docs/streaming/video-hosting/protect-your-videos-with-the-aes-128-encryption.md): Enable AES-128 encryption for HLS video delivery by configuring a keyserver to retrieve decryption keys via Gcore API, with EXT-X-KEY tags added to m3u8 playlists and optional country or domain access policies for additional security. - [HEVC, AV1, and VP9 multi-codec VOD](https://gcore.com/docs/streaming/video-hosting/multi-codec.md): Create HEVC, AV1, and VP9 video renditions from H.264 source videos using premium transcoding to reduce CDN bandwidth costs, with adaptive bitrate selection across multiple resolutions and codec priorities via HLS manifests. - [HLS, MPEG-DASH, and MP4](https://gcore.com/docs/streaming/video-hosting/hls-and-mp4.md): Configure HLS MPEG-TS, HLS CMAF, MPEG-DASH, and MP4 video formats in Gcore Video Streaming for VOD delivery with adaptive bitrate, codec support (H264, H265, AV1), manifest generation (.m3u8, master-cmaf.m3u8), and DRM encryption. - [Create an illusion of a live broadcast with uploaded videos](https://gcore.com/docs/streaming/video-hosting/create-an-illusion-of-a-live-broadcast-with-uploaded-videos.md): Configure Live imitation in Gcore Video Streaming to broadcast uploaded videos at scheduled start dates and times with automatic timezone detection, iframe player embedding, and sequential video playback from playlists up to 512 videos. - [Videos with multiple audio tracks](https://gcore.com/docs/streaming/video-hosting/multi-audio.md): Deploy VOD assets with multiple embedded audio tracks in HLS and DASH manifests, with automatic language metadata extraction, audio codec transcoding across ABR qualities, and player UI language selection for multilingual content distribution. - [Create and configure playlists for videos](https://gcore.com/docs/streaming/video-hosting/create-and-configure-playlists-for-videos.md): Create and configure video playlists in Gcore Streaming Platform by enabling the feature, adding up to 512 videos to a playlist via the portal Editor, reordering videos by drag-and-drop, and exporting embed code for website integration. - [Video Lifecycle and Statuses](https://gcore.com/docs/streaming/video-hosting/vod-status.md): Track video and rendition statuses throughout the VOD lifecycle - empty, uploading, processing, ready, and failed states; renditions transition from transcoding to finished or failed with mp4_url availability and HLS/DASH manifest updates via the videos API. - [Subtitles and closed captions for VOD](https://gcore.com/docs/streaming/video-hosting/subtitles-and-closed-captions-for-vod.md): Configure subtitles and closed captions for VOD videos using SRT and WebVTT timed text track formats in Gcore Player, with support for AI-generated subtitles, automatic translation, and third-party caption file attachment. - [Timeline hover previews: use with players and Roku devices](https://gcore.com/docs/streaming/video-hosting/timeline-hover-previews-use-in-players-and-roku-devices.md): Enable timeline hover previews (trick play) in Gcore Streaming Platform using WebVTT format via Get video API with storyboard tiles and VTT coordinates, or embed tiles in HLS .m3u8 manifests for Roku trick play specification compliance. - [Upload video via API to VOD storage](https://gcore.com/docs/streaming/video-hosting/upload-video-via-api.md): Upload videos to Gcore Video Hosting via API using three methods - copy from external storage, upload from local device, or batch upload for migration; specify input parameters, codecs, protocols, video/audio profiles, GOP structure, bitrate constraints, and set account-level priority for transcoding queue scheduling. --- # Gcore DDoS protection > Protect servers and Virtual Machines against DDoS attacks using Gcore Advanced DDoS Protection with traffic redirection to a mitigation system for filtering attack traffic. - [DDoS protection](https://gcore.com/docs/ddos-protection.md): Protect servers and Virtual Machines against DDoS attacks using Gcore Advanced DDoS Protection with traffic redirection to a mitigation system for filtering attack traffic. - [About DDoS Protection](https://gcore.com/docs/ddos-protection/about-ddos-protection.md): Enable DDoS Protection with Basic protection (default, null-routing) or Advanced protection (always-on mode) to defend servers against amplification attacks, IP spoofing, volumetric L3 attacks, L4 connection attacks, and L7 application-layer attacks via Traffic Management System filtering. ## Onboarding service - [Service activation](https://gcore.com/docs/ddos-protection/onboarding-service/service-activation.md): Enable DDoS Protection service activation through Onboarding workflow including plan activation, network submission, NOC review, and network configuration steps. - [Plan activation](https://gcore.com/docs/ddos-protection/onboarding-service/plan-activation.md): Activate a DDoS Protection tariff plan in the Gcore customer portal by selecting a plan, entering payment card details, and completing activation with a 7-day free trial period. - [Network submission](https://gcore.com/docs/ddos-protection/onboarding-service/network-submission.md): Submit networks for DDoS protection by providing CIDR notation, AS number, and Letter of Authorization (LOA) PDF document; networks enter Pending status until NOC team approval. - [Review and approval](https://gcore.com/docs/ddos-protection/onboarding-service/review-and-approval.md): Manage NOC review and approval workflow for AS number and network CIDR registration, including submission validation, LOA document verification, and email notification status tracking. - [Network configuration](https://gcore.com/docs/ddos-protection/onboarding-service/network-configuration.md): Configure GRE endpoint IP address and select protection profile (Basic or custom) for DDoS Protection protected networks via Gcore Customer Portal. - [Configure a custom protection profile](https://gcore.com/docs/ddos-protection/onboarding-service/custom-protection-profile-configuration.md): Configure custom DDoS protection profiles with rules and policies to match network traffic criteria and apply protocol-aware protections for gaming protocols including Minecraft, Counter-Strike 1.6, Counter-Strike GO, Counter-Strike 2, and Left 4 Dead 2. - [Apply a custom profile to a protected network](https://gcore.com/docs/ddos-protection/onboarding-service/apply-a-custom-profile-to-a-protected-network.md): Assign a custom protection profile to a protected network in DDoS Protection via the Gcore Customer Portal by editing the network and selecting the profile from the Profile list. ## GRE tunneling - [About Gcore's DDoS protection with GRE tunneling and BGP routing](https://gcore.com/docs/ddos-protection/onboarding-service/gre-tunneling/about-gcore-ddos-protection-with-gre-tunneling-and-bgp-routing.md): Configure GRE tunneling and BGP routing to protect network infrastructure from DDoS attacks globally, managing GRE encapsulation, MTU/MSS limits, and BGP autonomous system routing between endpoints. - [Set a GRE tunnel with Gcore](https://gcore.com/docs/ddos-protection/onboarding-service/gre-tunneling/set-a-gre-tunnel-with-gcore.md): Configure GRE tunnel between Cisco routers with tunnel ID, source/destination IP addresses, MTU 1476 bytes, MSS 1436 bytes, and BGP peering session with AS numbers and prefix-list policies for route advertisement. - [Troubleshooting](https://gcore.com/docs/ddos-protection/onboarding-service/troubleshooting.md): Resolve network submission failures, pending status delays, configuration save errors, and custom profile visibility issues by validating CIDR format, AS Number ranges, LOA file size, GRE endpoint IP addresses, and protection profile selection. ## Super transit - [Super transit](https://gcore.com/docs/ddos-protection/super-transit.md): Deploy Super Transit to filter DDoS attacks via anycast routing and GRE tunneling while optimizing legitimate traffic routing through Gcore's global backbone for reduced latency. - [Configure your infrastructure for Super Transit](https://gcore.com/docs/ddos-protection/super-transit/configure-super-transit.md): Configure Super Transit with anycast tunneling, MSS clamping, IRR entries, and ASN validation to protect on-premises, hybrid, and cloud networks from DDoS attacks while optimizing traffic delivery through Gcore DDoS Protection. - [Gcore radar reports methodologies](https://gcore.com/docs/ddos-protection/gcore-radar-reports-methodologies.md): Analyze DDoS attack patterns in Gcore Radar reports using attack origin and victim country geolocation, targeted industry classification, attack characteristics including duration and power metrics, and attack type identification for UDP, ICMP, and SYN flood vectors. - [DDoS events log](https://gcore.com/docs/ddos-protection/events-log.md): View DDoS Protection events log in Gcore Customer Portal to access attack details including start time, BPS, PPS, attacked IP address, and attacking IP count for incidents within the past three months. --- # Gcore Edge Proxy > Deploy Edge Proxy DDoS protection on Gcore CDN edge infrastructure using Anycast IP addresses, translation rules mapping origin IP/port/protocol/application type, and globally distributed Points of Presence for multi-terabit filtering capacity. - [Overview](https://gcore.com/docs/edge-proxy/overview.md): Deploy Edge Proxy DDoS protection on Gcore CDN edge infrastructure using Anycast IP addresses, translation rules mapping origin IP/port/protocol/application type, and globally distributed Points of Presence for multi-terabit filtering capacity. - [Setup and configuration](https://gcore.com/docs/edge-proxy/setup-and-configuration.md): Configure Edge Proxy protection by specifying origin server IP address, port number (1–65535), protocol (TCP or UDP), and application type (Minecraft, Counter-Strike, Rust, Teamspeak, etc.) to receive a protected IP -PORT endpoint and activate DDoS mitigation. - [FAQs and trobleshooting](https://gcore.com/docs/edge-proxy/faqs-and-trobleshooting.md): Configure Edge Proxy DDoS protection for TCP and UDP applications by assigning protected Anycast IP addresses, creating proxy rules with application type selection, and updating DNS A or AAAA records to route traffic through Gcore CDN edge network Points of Presence. --- # Gcore WAAP > Protect websites, web applications, and APIs against application-layer attacks, bots, API abuse, and vulnerabilities using Gcore WAAP with real-time traffic inspection, WAF policies, behavioral analysis, rate limiting, bot management, API discovery, IP allowlists/denylists, and threat intelligence. - [Overview](https://gcore.com/docs/waap/overview.md): Protect websites, web applications, and APIs against application-layer attacks, bots, API abuse, and vulnerabilities using Gcore WAAP with real-time traffic inspection, WAF policies, behavioral analysis, rate limiting, bot management, API discovery, IP allowlists/denylists, and threat intelligence. ## Getting started - [Configure WAAP for a new domain](https://gcore.com/docs/waap/getting-started/configure-waap-for-a-domain.md): Create a Gcore CDN resource with WAAP enabled by specifying domain name, origin server IP or hostname, origin authentication type, and custom port settings, then update DNS records with the generated CNAME to route traffic through WAAP for Layer 7 DDoS protection and web application security. - [Manage domains protected with WAAP](https://gcore.com/docs/waap/getting-started/manage-domains.md): Manage WAAP-protected domains in CDN resources by toggling protection status (Monitoring, Protection, Disabled), disabling WAAP via Security section or Rules tab, and deleting inactive domains after disabling protection in Gcore Customer Portal. - [Billing](https://gcore.com/docs/waap/getting-started/billing.md): Configure WAAP billing plans (Free, Start, Pro, Enterprise) with feature availability for IP Firewall, Default Rules, Custom Rules, Bot Management, Threat Intelligence, and API Security; manage Domain/Zone billing units representing CDN resources with single WAAP configurations. ## Analytics - [WAAP Analytics](https://gcore.com/docs/waap/analytics/waap-analytics.md): Monitor WAAP-protected domains and APIs with Analytics Dashboard, Events investigation, and Domains coverage views displaying security posture, attack detection, mitigation actions, and traffic patterns in UTC timezone. - [Dashboard](https://gcore.com/docs/waap/analytics/dashboard.md): Monitor WAAP traffic across account-level and domain-level scopes using Dashboard metrics including total requests, detected attacks, prevented attacks, passed requests, traffic timeline, and top activity indicators by source country, attacker, target, and triggered rules. - [Events](https://gcore.com/docs/waap/analytics/events.md): Investigate HTTP requests and security events in WAAP using Events filters by time range, event type, decision (Blocked, Monitored, Allowed, Passed), optional action (CAPTCHA, JS Challenge), country, IP address, path, HTTP method, response code, request ID, reference ID, and session ID with 30-day retention. - [Domains](https://gcore.com/docs/waap/analytics/domains.md): Manage protected assets in WAAP by selecting domains to isolate analytics, security events, and incident investigation for specific applications, APIs, and services across production, staging, and multi-tenant environments. ## Firewall - [Access control](https://gcore.com/docs/waap/firewall/access-control.md): Configure WAAP Firewall allowed and blocked IP lists to permit or deny traffic from specific IPv4, IPv6 addresses, or IP ranges before requests reach your application. - [IP Reputation](https://gcore.com/docs/waap/firewall/ip-reputation.md): Configure IP Reputation policies in Gcore WAAP to block or challenge traffic from TOR networks, proxy networks, hosting services, VPNs, malicious bots, suspicious NAT ranges, external reputation block lists, and CDN infrastructure using JavaScript validation and automatic blocking. - [Check IP](https://gcore.com/docs/waap/firewall/check-ip.md): Check IP reputation tags and detection activity in WAAP Firewall, viewing local and global reputation tags (suspectedautomation, rapidbehaviour, ipinjectedfastclient, lowriskip) assigned to detected IP addresses with timestamps and associated domains. - [L7 DDoS protection](https://gcore.com/docs/waap/ddos-protection.md): Detect and mitigate Layer 7 DDoS attacks on web applications, websites, and APIs using WAAP Monitoring and Protection modes with automatic DDoS mode activation based on global traffic thresholds and attack pattern analysis. ## Default Rules - [WAAP policies](https://gcore.com/docs/waap/waap-policies.md): Configure WAAP policy groups to block malicious traffic, common attack patterns, data breaches, unauthorized access, suspicious IPs, and bot traffic by enabling or disabling specific policies. - [OWASP threats](https://gcore.com/docs/waap/waap-policies/waf-and-owasp-top-threats.md): Configure OWASP Threats policies in Gcore WAAP to detect and block SQL injection, cross-site scripting (XSS), shellshock exploits, open redirects, and personally identifiable information (PII) leakage via the Default Rules tab in Customer Portal. - [Behavioral WAF](https://gcore.com/docs/waap/waap-policies/behavioral-waf.md): Configure Behavioral WAF policies in WAAP to block brute-force attacks, probing, obfuscated injection attacks, and repeated violations using CAPTCHA and JavaScript validation challenges. - [CMS protection](https://gcore.com/docs/waap/waap-policies/cms-protection.md): Configure CMS Protection policy group in WAAP to allowlist logged-in administrators for WordPress, MODX, and Drupal while blocking WordPress exploits and SQL injection attacks via the Gcore Customer Portal. ## Custom Rules - [WAAP rules](https://gcore.com/docs/waap/waap-rules.md): Create WAAP firewall rules, custom rules, and advanced rules to inspect web requests by IP address, country, request length, strings, SQL injection patterns, XSS payloads, and predefined tags, then apply actions like block, allow, or CAPTCHA challenge. - [Custom Rules](https://gcore.com/docs/waap/waap-rules/custom-rules.md): Create WAAP custom rules with conditions and actions (Allow, Block, CAPTCHA, JS Challenge, Tag) to control access by URL, country, organization, and IP; configure rate limit rules to restrict requests per time range; apply tag rules for monitoring and analytics with priority-based action enforcement. - [Rate-Limiting](https://gcore.com/docs/waap/waap-rules/advanced-rules/advanced-rate-limiting-rules.md): Configure rate-limiting rules in WAAP using the request.limit_rate method to control request counts by time window, IP origin, URL patterns, request methods, response status codes, aggregation scope, and tags via the Gcore WAAP API. ## Advanced rules - [Advanced Rules](https://gcore.com/docs/waap/waap-rules/advanced-rules.md): Create advanced WAAP rules using Common Expression Language (CEL) syntax via API with If/Then conditions, rule objects, source field objects, and single-action enforcement (allow, deny, log, challenge, or block). - [Advanced rule objects and attributes](https://gcore.com/docs/waap/waap-rules/advanced-rules/advanced-rule-objects.md): Configure advanced rule objects and attributes including client_data fingerprint, request rate_limit with content_type/interval/ip_list/method_list/requests/scope/status_list/url parameters, and response headers/status for WAAP rule conditions. - [Source field objects in advanced rule expressions](https://gcore.com/docs/waap/waap-rules/advanced-rules/source-field-objects.md): Configure advanced rule expressions using source field objects (request.headers, request.ip, request.uri, request.path, request.method, request.origin_ip, request.ja3) with single-quoted string values in WAAP rule conditions. ## Tag rules - [Tag rules](https://gcore.com/docs/waap/waap-rules/custom-rules/tag-rules.md): Create tag-based and tag-generating rules in WAAP custom rules to filter incoming traffic using predefined tags, user-defined tags, request headers, and cookies for blocking or allowing requests to domains. - [Reserved tags](https://gcore.com/docs/waap/waap-rules/custom-rules/tag-rules/reserved-tags.md): Configure reserved tags in WAAP custom rules to trigger specific actions - general tags (Registered, Logged In, Paid, Monitor, Login Page, Malicious Activity, Item Added to Cart) and API protection tags (API Privileged Access, API Admin Access, Auth Endpoint, Ignore Email Address Detection) using conditions like IP address, session cookies, or HTTP response headers. - [Predefined tags and their descriptions](https://gcore.com/docs/waap/waap-rules/custom-rules/tag-rules/predefined-tags.md): Configure tag-based rules in WAAP using predefined behavioral tags including abnormaldynamicrequests, ajaxscraper, botnetclient, bruteforceattempt, captchafarmbotfp, automationdriver, and 40+ additional tags generated by heuristics and AI models to filter and sanction web requests via Customer Portal or API. ## Bot Management - [Bot Protection](https://gcore.com/docs/waap/troubleshooting/enable-troubleshoot-bot-protection.md): Enable Gcore WAAP bot protection using User-Agent detection, traffic source analysis, behavioral analysis, and headless browser detection to block unauthorized vulnerability scans; manage Known Bots allowlist and configure Lets Encrypt policy via Bot Management portal. - [Known Bots](https://gcore.com/docs/waap/waap-policies/known-bots.md): Configure Known Bots policy in WAAP Bot Management to allow or block traffic from legitimate automated services including Google, Microsoft, Slack, Facebook, Twitter crawlers, SEO tools, and PayPal IPN requests by setting policy mode to Allow or Policy-based. - [Anti-automation and bot protection](https://gcore.com/docs/waap/waap-policies/anti-automation-and-bot-protection.md): Configure WAAP Bot Management policies including Anti-spam, Traffic anomaly, Automated clients, Headless browsers, Anti-scraping, and Vulnerability Scanner rules via behavioral WAF and JavaScript injection to block non-human traffic while allowing known bots. - [Invalid user agent and unknown user agent](https://gcore.com/docs/waap/waap-policies/invalid-user-agent-and-unknown-user-agent.md): Configure WAAP Invalid user agent and Unknown user agent policies to block requests with missing or non-standard user-agent headers that indicate illegitimate clients. ## Threat Intelligence ## Security Insights - [Security Insights](https://gcore.com/docs/waap/threat-intelligence/security-insights/security-insights.md): Enable Security Insights notifications in WAAP to identify domain misconfigurations, rule mismanagement, and security vulnerabilities with system-generated recommendations for Enterprise plan domains. - [View and investigate insights](https://gcore.com/docs/waap/threat-intelligence/security-insights/view-insights.md): View and investigate WAAP Security Insights including Attack on disabled policy and Allowed high-risk IP insight types, filtered by status (Unread, Read, Closed) and displayed with description, recommendation, IP address or Policy ID, and alert timestamps in the Gcore Customer Portal. - [Manage insight status](https://gcore.com/docs/waap/threat-intelligence/security-insights/manage-insights.md): Manage WAAP security insight status by marking as read, silencing for custom periods at entity or rule level, closing with 30-day auto-deletion, and reopening closed insights via Status dropdown. - [Manage Silence Rules](https://gcore.com/docs/waap/threat-intelligence/security-insights/manage-silence-rules.md): Manage Silence Rules in WAAP Security Insights to modify silence duration, delete rules, or unsilence alerts for Attack on disabled policy and Allowed high-risk IP insight types via Gcore Customer Portal. - [IP Spotlight](https://gcore.com/docs/waap/ip-security/ip-spotlight.md): Analyze IP addresses using IP Spotlight threat analytics to retrieve risk assessment scores, global and domain activity, WHOIS data, botnet involvement, and threat tags (SQL injection, DDoS, headless browsers) for WAAP policy configuration and WAF rule creation. ## API Protection - [API discovery and protection](https://gcore.com/docs/waap/api-discovery-and-protection.md): Configure Gcore WAAP API Discovery, API base paths, and reserved tags to detect API endpoints, specify protection rules, and control access by user role. - [API discovery](https://gcore.com/docs/waap/api-discovery-and-protection/api-discovery.md): Manage REST API endpoints in WAAP domains using API Discovery to scan traffic, detect legacy and shadow APIs, validate endpoints, and import Swagger files; access API Baseline, Potential APIs, Scan History, and API Discovery Settings pages to confirm, reject, or manually add endpoints with statuses including Potential, Confirmed, Not an API, and Delisted. - [Configure API access and protection with reserved tags](https://gcore.com/docs/waap/api-discovery-and-protection/configure-api-access-with-reserved-tags.md): Configure API protection with reserved tags (API Privileged Access, API Admin Access, Indicate API Privileged User, Indicate API Admin User, Auth Endpoint, Ignore Email Address Detection, Ignore Phone Number Detection, Ignore CCN Detection, Ignore SSN Detection) via API Discovery or custom rules to categorize and manage API endpoint access by authorization level. - [Manually add endpoints to the API base path](https://gcore.com/docs/waap/api-discovery-and-protection/configure-api-base-path.md): Configure API base path endpoints in WAAP domains by manually adding recursive paths to define communication routes for API request protection, with support for domain-wide API settings or specific endpoint paths via the Customer Portal Settings tab. - [Advanced API protection](https://gcore.com/docs/waap/waap-policies/advanced-api-protection.md): Configure Advanced API protection policies in WAAP including Auth token protection, Sensitive data exposure, Invalid API traffic, and API-level authorization rules via the Gcore Customer Portal for Enterprise plan domains. - [Protocol validation](https://gcore.com/docs/waap/waap-policies/protocol-validation.md): Configure protocol validation rules in Gcore WAAP Bot Management to block non-compliant HTTP and HTTPS requests, including invalid user agents, malformed request methods, service protocol tampering, and requests violating HTTP RFC standards. ## Response pages - [Response pages](https://gcore.com/docs/waap/response-pages.md): Configure WAAP response pages including Browser validation, Enable cookies, Enable JavaScript, Captcha, Block, and Block CSRF pages triggered by WAAP policies and custom rules, with customizable priority order and corporate branding options. - [Create custom response pages](https://gcore.com/docs/waap/response-pages/create-custom-response-pages.md): Create custom WAAP response pages with personalized content for Block, Block CSRF, Captcha, Enable cookies, Browser validation, and Enable javascript page types, configurable at account level with browser title, page title, and custom messaging up to 6 page sets per account. - [Manage custom response pages](https://gcore.com/docs/waap/response-pages/manage-custom-response-pages.md): Manage custom response pages at account and domain levels in Gcore WAAP, including switching active page sets, modifying page statuses (Active/Inactive), and updating page set assignments to domains via the Customer Portal. ## FAQs - [Frequently asked questions](https://gcore.com/docs/waap/frequently-asked-questions.md): Configure WAAP JavaScript injection, required cookies, and storage variables for bot detection and session management. - [How does WAAP JavaScript injection work?](https://gcore.com/docs/waap/frequently-asked-questions/javascript-injection.md): Configure WAAP JavaScript injection to collect client fingerprint, browser-type signature, and GUI interaction data via cookie-based tracking and /sbbi/ endpoint requests for bot detection and malicious traffic filtering. - [What are the required cookies used by WAAP?](https://gcore.com/docs/waap/frequently-asked-questions/waap-cookies.md): Configure Gcore WAAP cookies for session management, CSRF protection, CAPTCHA validation, DDoS protection, and load balancing using Set-Cookie response headers with HttpOnly, SameSite, and path attributes. - [What storage variables does WAAP use?](https://gcore.com/docs/waap/frequently-asked-questions/storage-variables.md): Configure WAAP local storage variables including cnv, csr, otr, and altutgv2 for CAPTCHA validation, shell mouse script tracking, and user tag token management in web browsers. - [Troubleshooting](https://gcore.com/docs/waap/troubleshooting.md): Troubleshoot Gcore WAAP bot protection enablement, blocked user access, and 5xx server errors with root cause analysis and resolution steps. - [Troubleshoot blocked users](https://gcore.com/docs/waap/troubleshooting/troubleshoot-blocked-users.md): Troubleshoot WAAP blocked users by searching Events requests table with Reference ID, IP address, and date-time metadata to inspect triggered policies, custom rules, HTTP method, client IP, country of origin, and user agent details in the Customer Portal. - [Troubleshoot 5xx errors](https://gcore.com/docs/waap/troubleshooting/troubleshoot-5xx-errors.md): Diagnose WAAP 5xx server errors including 543 errors caused by origin server downtime, firewall blocks, connection timeouts, and incorrect configuration settings.