Knowledge base
1000 FAQs, 500 tutorials and explanatory videos. Here, there are only solutions!
¡Gracias por elegir el servicio de venta de entradas de Infomaniak!
Esta herramienta te permite gestionar todos los aspectos de tu venta de entradas en lĂnea: la gestiĂłn de tus eventos, la creaciĂłn de una taquilla en lĂnea, el control de tus entradas y el seguimiento de tus ventas y clientes.
Esta guĂa te permite utilizar rápidamente las funciones esenciales. En caso de problemas, consulta nuestra base de conocimientos antes de ponerte en contacto con nuestro equipo de soporte.
ConfiguraciĂłn y gestiĂłn de la taquilla
- Crear tu taquilla
- Crear y gestionar un evento
- Crear eventos con mĂşltiples representaciones
- Asignar un plano de asientos a un evento
- CĂłmo utilizar los pases
- Gestionar ofertas promocionales
- Crear vales de regalo
- Gestionar métodos de pago
- Crear formularios de inscripciĂłn para clientes
VisualizaciĂłn de entradas y creaciĂłn de la taquilla en lĂnea
- Gestionar opciones de la taquilla en lĂnea
- Modificar la apariencia de la entrada
- Poner en lĂnea la taquilla en tu sitio web
GestiĂłn avanzada de eventos y pases
- GestiĂłn de zonas tarifarias
- Tarifas de grupo
Herramientas de marketing
- EnvĂo automático de emails 2 dĂas antes del evento
- Publicar eventos en el portal Infomaniak.events
- Portal Infomaniak: Agrupar eventos de tu taquilla
Venta y control de entradas
Venta directa y venta a través de revendedores
- Venta directa desde la taquilla
- Dar acceso a revendedores para vender directamente desde la taquilla
- Importar entradas de revendedores externos
Equipo de venta y control
- Pedir equipo de venta y control
- Formatos de entradas disponibles
- Configuración y uso de paquetes de venta: entradas para espectáculos y cine
- ConfiguraciĂłn y uso de la impresora para pases
- Escaneo de entradas - Dispositivo Android
- Escaneo de entradas con nuestros escáneres
GestiĂłn de solicitudes de clientes
- El cliente no puede pagar con tarjeta de crédito: Verificación a realizar
- Enviar un email o SMS a todos los visitantes de un evento
- Intercambiar entradas desde la taquilla
- Activar el intercambio de entradas en la taquilla para los visitantes
- Reembolso de clientes (prĂłximamente)
- Seguro de cancelaciĂłn
- Cancelar pedidos o entradas
Seguimiento de ventas y clientes
- Comprobar pedidos y ventas (prĂłximamente)
- Consultar estadĂsticas (prĂłximamente)
- Consultar informes de ventas
- Consultar comisiones de Infomaniak (prĂłximamente)
- Recibir extractos de los pagos de Infomaniak (prĂłximamente)
Uso avanzado
- API de la taquilla
- Conectar la taquilla con Zapier
- PersonalizaciĂłn avanzada de la taquilla en lĂnea (HTML, CSS o JS)
Preguntas frecuentes
- ¿Cuál es la diferencia entre la herramienta de venta de entradas y el gestor de invitados?
- ¿Cuáles son los costos reales de la venta de entradas?
This guide details the errors of type Rejected, too many connections from this host
if they occur while visiting a website.
Origin of the Errors
429 Too Many Requests
This error occurs when the server is overwhelmed by a large number of requests in a short period, which can be due to heavy usage of the site or abuse.
503 Service Temporarily Unavailable
This error can be caused by several factors, including scheduled maintenance work on the server, server overload due to high traffic, or the execution of a script that exceeds the server's resource limits.
Rejected, too many connections from this host
This error occurs when the server rejects connections due to a high number of simultaneous connections from the same IP address. Check "Access and Error Logs" on your hosting dashboard to find multiple entries like:
[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/blocktopmenu/js/superfish-modified.js current:34 limit:30
[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/blocktopmenu/js/hoverIntent.js current:34 limit:30
[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/productscategory/productscategory.js current:34 limit:30
[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/modules/feeder/rss.php current:35 limit:30
[Fri Sep 02 11:40:31] [error] [client 222.111.123.123] Rejected, too many connections from this host. (vhost:domain.xyz uri:/js/modules/favoriteproducts/favoriteproducts.js current:34 limit:30
In this example, the IP 222.111.123.123 is making 30 simultaneous connections on each page, therefore it is automatically rejected as this may resemble an attack or scan.
Resolution Steps
Some steps to resolve these errors:
- Check scripts that make multiple connections to the server to display data.
- Optimize the concerned script(s) so that they require fewer resources.
- Increase the limits of the concerned site to allow the script to do what it needs to do and/or limit the number of simultaneous connections (especially on a Cloud Server where limits - memory, execution time, simultaneous connections - can be significantly increased).
- Migrate your hosting to a Cloud Server.
This guide explains how to inject HTML code or use CSS or Javascript links to customize your online ticketing system.
Setting Up the Script
- Login to your Infomaniak account (manager.infomaniak.com)
- Go to Ticketing
- Access the Shop / Publish and Shop Option menu
- Click on Advanced Options
- HTML scripts should be placed directly in the fields provided for this purpose
- External CSS links and external JS can be specified below
Lists of Triggers
Here is a list of triggers for various services that you can use with HTML code
Learn More
This guide explains how to install the PageSpeed Insights tool on an Infomaniak Web Hosting.
The PageSpeed Insights tool from Google allows you to measure the loading time of a page on both mobile and desktop devices, while Google's PageSpeed Tools module is an open-source library that optimizes a site on the server using over 40 filters that correspond to best practices recommended by Google. Learn more
Install PageSpeed Tools
To activate Google's PageSpeed Tools:
- Log in to the Infomaniak Manager (manager.infomaniak.com) from a web browser like Brave or Edge
- Click on the icon in the top right corner of the interface (or navigate through the left side menu, for example)
- Select Website (universe Web & Domain)
- Click on the name of the relevant object in the displayed table
- Click on Advanced settings
- Click on the Apache tab
- Activate the Google Page Speed Optimization option
Default Configuration Enabled
ModPagespeedEnableFilters combine_css
ModPagespeedEnableFilters extend_cache
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters rewrite_css
ModPagespeedEnableFilters rewrite_javascript
ModPagespeedEnableFilters combine_javascript
ModPagespeedEnableFilters pedantic
ModPagespeedEnableFilters remove_comments
A caching system is also set up for site files. This is updated every 15 minutes.
If needed, it is possible to customize certain directives via the site's .htaccess file: https://modpagespeed.com/doc/configuration#htaccess
But beware, according to this Google thread and this discussion, unfortunately mod_pagespeed does not take into account directives in a ".htaccess" file when accessing a dynamic file. To no longer have mod_pagespeed, it must be disabled from the Manager.
Known Incompatibilities
- ownCloud
- WP Rocket
Furthermore, it is not abnormal if warnings appear after installing PageSpeed:
"By default, mod_pagespeed will fetch css/js/images using http. If the webserver doesn't respond within 50ms (by default), it will abort the request, and log the timeout messages you are seeing..."
In a shared environment, it is not worrying or abnormal to slightly exceed the 50ms response time.
Learn More
This guide gives you the list of triggers to use to link a tracker such as Google Tags and Facebook Pixel from your Infomaniak ticketing service.
These triggers must be inserted in the HEAD part of the advanced options on your shop. For more information on this subject, see the guide to inserting HTML codes into your ticketing service.
Examples with Google Tags and Facebook Pixel
External documentation for Facebook Pixel
Example of the code to insert in the Facebook Pixel ticketing service:
!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
document,'script','https://connect.facebook.net/en_US/fbevents.js');
document.addEventListener("ike_event_view", function( e ) {
fbq('init', '14085424191xxxxx');
fbq('track', "PageView");
fbq('track', 'InitiateCheckout');
});
document.addEventListener("ike_cart_payment_launched", function( e ) {
fbq('init', '14085424191xxxxx');
fbq('track', "PageView");
fbq('track', 'Purchase', {value: e.detail.topaid, currency: e.detail.currency.name});
});
Example with Google analytics with gtag.js :
External documentation for Google tags :
- https://developers.google.com/analytics/devguides/collection/gtagjs/
- https://developers.google.com/analytics/devguides/collection/gtagjs/events
Example of the code to insert in the ticketing service for Google Tags :
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-xxxxxxx-x');
document.addEventListener("ike_event_view", function( e ) {
gtag('event', 'view_item', {
'event_category' : e.name,
'event_label' : e.date
});
});
document.addEventListener("ike_cart_add", function( e ) {
gtag('event', 'add_to_cart');
});
document.addEventListener("ike_cart_confirm", function( ) {
gtag('event', 'checkout_progress', {
'event_category' :'valid cart'
});
});
document.addEventListener("ike_cart_payment_launched", function( e ) {
gtag('event', 'add_payment_info', {
'event_category' : 'paiement',
'event_label' : e.detail.currency.name,
'value': e.detail.topaid
});
});
List of the the triggers :
Home page:
trigger : ike_home_view
Datas : none
//send to your tracking tool
});
Event page:
Page of an event with multiple dates
trigger : ike_event_view
Datas : detail.name
console.log(e.detail.name);
//send to your tracking tool
});
Date page:
Page of a date of an even
trigger : ike_date_view
Datas : detail.name, detail.date
document.addEventListener("ike_home_view", function(e) {
console.log(e.detail.name, e.detail.date);
//send to your tracking tool
});
Pass page:
Page of a pass category
trigger : ike_abo_view
Datas : detail.name
console.log(e.detail.name);
//send to your tracking tool
});
Pass selection page:
Page of passes dates selection
trigger : ike_abo_selection
Datas : detail (cart details)
console.log(e.detail.name, e.detail.date);
//send to your tracking tool
});
User login:
Triggered login success
trigger : ike_user_login
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
User logout:
trigger : ike_user_logout
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart add:
Triggered when element added to cart
trigger : ike_cart_add
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart page:
trigger : ike_cart_view
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart update:
Triggered when a cart element is updated
trigger : ike_cart_update
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart empty:
Triggered when empty button pressed
trigger : ike_cart_empty
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart confirm:
Triggered when confirm button pressed
trigger : ike_cart_confirm
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart delivery page:
trigger : ike_cart_delivery_view
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart form page:
trigger : ike_cart_form_view
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart payment page:
trigger : ike_cart_payment_view
Datas : detail (cart details with paymentMethodSelected)
console.log(e.detail);
//send to your tracking tool
});
Cart payment changed:
trigger : ike_cart_payment_changed
Datas : detail.path
document.addEventListener("ike_cart_payment_changed", function(e) {
console.log(e.detail);
//send to your tracking tool
});
Cart payment launched:
trigger : ike_cart_payment_launched
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart payment success page:
trigger : ike_cart_payment_success
Datas : detail (cart details)
console.log(e.detail);
//send to your tracking tool
});
Cart delete item:
trigger : ike_cart_delete
Datas : detail (previosCart and newCart)
console.log(e.detail);
//send to your tracking tool
});
Page Changed:
trigger : ike_page_changed
Datas : detail.path
console.log(e.detail);
//send to your tracking tool
});
Learn more
This guide explains how to activate a CDN to optimize an Infomaniak Web Hosting.
What is a CDN?
CDN stands for "Content Delivery Network" in English, which translates to "Red de DistribuciĂłn de Contenido" in Spanish and "Content Delivery Network" in Italian. A CDN stores a copy of your site's content (images, videos, CSS/JS files) on multiple servers geographically dispersed. When a user accesses your site, the CDN provides this content from the server closest to their location, thereby reducing loading times.
Advantages of a CDN
- Improved loading speed: your site loads faster for visitors, which can reduce bounce rates and improve user experience.
- Reduced load on your origin server: by distributing content, the CDN lightens the load on your main server, improving its performance and availability.
- Increased security: some CDNs offer security features such as protection against DDoS attacks and data security.
Setting up a CDN
To use a CDN, you will generally need to make adjustments to your domain name configuration, specifically at the DNS records level. This will redirect your site's traffic to the CDN's network of servers. So in general:
- Create an account on the CDN's website of your choice and add your site.
- Modify the DNS zone of your domain name according to the instructions provided by the CDN.
- Test your site to ensure that the CDN is working correctly.
Cloudflare
Cloudflare CDN optimizes the performance and security of a website. It is a reverse proxy, which means that once your site starts using CloudFlare, the traffic it receives is routed through CloudFlare's network. Additionally, Cloudflare provides the following features:
- Caching of a site's static content
- Minification of HTML, CSS, and Javascript code
- Basic DDoS protection
- etc.
To set up Cloudflare:
- If necessary, create an account with Cloudflare: https://www.cloudflare.com/sign-up
- Add the domain name of the site in question.
- Transfer all the DNS zone records of the domain in question to Cloudflare (A, MX, TXT, NS, etc.).
- In the Infomaniak Manager, modify the DNS zone of the domain in question with the DNS servers indicated by Cloudflare.
It may take up to 48 hours for the new DNS to take effect.
Note: mod_cloudflare is enabled by default on all our paid Web Hosting plans.
Amazon CloudFront
If you are already using AWS services, CloudFront is easy to set up. Create a distribution, configure the settings, and link it to your site.
Fastly
Sign up for Fastly, configure your service by adding your site, and define cache settings. Fastly offers advanced configuration options.
This guide explains how to redirect all visitors to a secure HTTPS version of a website hosted on Infomaniak Web Hosting.
This redirection is usually automatic with standard configuration and installation ⚠️ For additional help contact a partner or fill out a tender — also read the role of the host.
Prerequisites
- Have a valid and functional SSL certificate for the Infomaniak website
Manual Redirection using .htaccess file
Simply modify or add the following 3 lines to the .htaccess file of the concerned website so that all its visitors automatically access its secure HTTPS version:
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteRule (.*) https://domain.xyz/$1 [R=301,L]
- Replace the second line of the above code with RewriteCond %{HTTP:X-Forwarded-Proto} !https in case of any issues
With a CMS
Most web applications like WordPress and Joomla have extensions/plugins that automatically redirect visitors from a site to its secure HTTPS version.
WordPress
If you're using a Content Management System (CMS) like WordPress to build your site, we recommend installing an extension to perform this redirection:
- Backup the site files and database as a precaution
- Install the Really Simple SSL or similar extension from the WordPress console and activate it
- Visitors will now be automatically redirected to the HTTPS version of the site
- In case of confirmed issues (persistent after clearing cache, etc.), you can also use Velvet Blues update URLs
Joomla
- Find the line var $live_site =''; in the Joomla configuration file (configuration.php) on the server
- Replace it with var $live_site = 'https://www.domain.xyz';
- Add three lines to your .htaccess file on the server:
RewriteEngine On
RewriteCond %{HTTPS} OFF
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - Open the Joomla administration panel under "System - Configuration"
- Click on the "Server" tab and under "Force SSL" choose "Administration and Site"
- Save, and visitors will now be automatically redirected to the HTTPS version of the site
Prestashop
- Access general settings in the Prestashop back-office to enable SSL:
- < v1.7 click on "Preferences" then "General"
- > v1.7 click on "Shop Parameters" then "General"
- Switch the "Enable SSL" button to "YES"
- Click on "Save"
- In the same place, switch the "Enable SSL on the entire site" button to "YES"
- Click on "Save"
If a security padlock does not appear in the browser or a warning is displayed, check the template or modules as sometimes they may not be fully compatible with SSL. Your Prestashop might then load elements (images, .css or .js files, fonts...) via "http" instead of "https" which should now be loaded.
Drupal
This article explains how to move a Drupal site from http to https.
Alternative Solutions
Replace domain.xyz with your domain name including the appropriate extension (.com, .fr, .ch, etc.)
In your .htaccess file, to force the site URL to be https:// but without www:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www. [NC]
RewriteRule (.*) https://domain.xyz/$1 [R=301,L]
In case of a redirection loop, adjust the above code to:
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} ^www. [NC]
RewriteRule (.*) https://domain.xyz/$1 [R=301,L]
In your .htaccess file, to force redirection with www
with subdomains:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule (.*) https://www.domain.xyz/$1 [R=301,L]
In case of a redirection loop, adjust the above code to:
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule (.*) https://www.domain.xyz/$1 [R=301,L]
and without subdomains:
RewriteEngine on
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^domain.xyz [NC]
RewriteRule (.*) https://www.domain.xyz/$1 [R=301,L]
In case of a redirection loop, adjust the above code to:
RewriteEngine on
RewriteCond %{HTTP:X-Forwarded-Proto} !https [OR]
RewriteCond %{HTTP_HOST} ^domain.xyz [NC]
RewriteRule (.*) https://www.domain.xyz/$1 [R=301,L]
Common Errors after HTTPS Redirection
To resolve common issues that may occur after redirecting your website to its secure HTTPS version, refer to this guide (click here).