In this article, you will learn:
WEDOS-Protected Websites
WEDOS Protection is primarily used to protect websites and through that the underlying web hosting infrastructure from attacks and other unwanted traffic. This is achieved by:
- Filtering suspicious traffic based on IP or behavior. WEDOS Protection valuta tutto il traffico con un algoritmo complesso. A volte le vie e i metodi di attacco sono piuttosto evidenti, altre volte si camuffano per sembrare il più legittimi possibile e confondersi tra i bot utili e i visitatori autentici del sito. Poiché è meglio peccare di prudenza, il sistema può talvolta bloccare traffico non dannoso e rendere il sito non disponibile per un certo gruppo di visitatori o servizi.
- Delivering cached content. Per ridurre il carico dei server, WEDOS Protection mette in cache i contenuti, il che può causare la visualizzazione di versioni non aggiornate del sito, soprattutto se il contenuto in cache viene richiesto molto spesso. Per ulteriori informazioni leggi Protection – CDN Cache article.
- Hiding the web server behind a proxy. L’IP del server di un sito protetto dovrebbe essere completamente nascosto da Internet e sostituito dall’IP del server proxy WEDOS Protection. Questo può tuttavia diventare un problema quando un servizio deve verificare che l’IP del web hosting corrisponda ai record del dominio. Per ulteriori informazioni consulta Protection – DNS and Target IPs article.
- HTTPS. Il sistema impone l’uso del protocollo sicuro HTTPS (HTTP su SSL) e può generare errori se la cifratura non riesce in un qualsiasi punto.
You typically activate the protection and other benefits of WEDOS Protection by adding your domain, ma WEDOS può anche attivare una versione di emergenza in casi giustificati.
Emergency WEDOS Global
When an unprotected website operated primarily on a shared Webhosting service becomes the target problematic traffic or an attack that threatens other parts of the infrastructure outside of that website, we must minimize the damage by significantly limiting this problematic website, sometimes even shutting it down completely. This solution is disadvantageous for both us and the customer.
WEDOS Protection allows us to bypass the need for operational restrictions using the mechanisms listed above, which protect the website itself and all related infrastructure, because the attack now has to go through a proxy that is properly equipped to deal with it, and the web server has free resources to do what it’s meant to be doing.
To deploy this protection, we need the Webhosting domain to use WEDOS DNS servers ⧉. In caso di emergenza, un tecnico modificherà nel nostro sistema i record DNS dal web server al proxy WEDOS Protection: di solito questo risolve il traffico indesiderato in pochi minuti e può rimuovere eventuali limitazioni dell’hosting.
We inform customers about the action taken by a message sent to their billing email address.
While Emergency WEDOS Protection is technically free, it comes with these major drawbacks:
- No customer control over WEDOS Protection settings. Unless customers purchase WEDOS Protection for themselves, they don’t have access to controls.
- Eventuali problemi vengono gestiti dall’assistenza clienti con priorità bassa. Typical response time in case of content issues is 2 hours, may take significantly longer during weekends or holidays.
To enjoy the benefits of WEDOS Protection for free, without any drawbacks of the emergency version, add the domain via our WordPress plugin.
Emergency WEDOS Protection deployment may cause errors. The most common ones, including their solutions, can be found in the Troubleshooting chapter.
Troubleshooting Common Issues
Common issues with sites using WEDOS Protection, either as a stand-alone service or the emergency version deployed by us, include:
- Error messages
- Damaged or dysfunctional website contents
- Accesso bloccato a contenuti e API di terze parti
- Spammed or undelivered emails sent from web
Error Messages
Issue: Sul sito viene visualizzato un messaggio di errore.
Solution: The correct solution depends on the displayed error message:
- Not found on accelerator. You will most often encounter this error if you do not have HTTPS set up on your VEDOS Webhosting. Check the domain settings in the certificate according to the Webhosting – Manual HTTPS Setup ⧉ guide. If HTTPS is disabled, enable it. If there are errors with domains, contact support ⧉ and ask to add (sub)domains with disabled validation.
- Not found (404). This error is caused either by incorrect HTTPS settings on the target server (see above), or WEDOS.protection reverse proxy IPs. In the latter case, make sure that your proxy IPs match those set in the domain’s DNS.
- Gateway Timeout. Make sure your server is not blocking connections to addresses from this list ⧉ (JSON version ⧉).
Website Contents
Issue: The website does not display correctly or at all after deploying WEDOS Protection. Sometimes only the main page or some subpages work correctly.
Cause: The problem is usually caused by a static content caching error, but it can also be related to the blocking of templates, plugins, and external resources described below.
Solution: If you have access to the domain’s WEDOS Global admin panel ⧉, svuota la cache o reimpostala (disattiva e riattiva) in CDN Cache settings.
If you do not have access to the WEDOS Global administration, you can add the domain and gain access, oppure ask us to purge the cache ⧉. Le richieste di solito vengono risolte dal reparto tecnico entro 2 ore, a seconda del carico di lavoro del reparto e della complessità della soluzione (soprattutto se il problema si trova altrove).
Blocco dei contenuti esterni
Issue: Dopo l’attivazione di WEDOS Protection, un template, un plugin o un servizio/API di terze parti (crawler, gateway di pagamento e simili) non funziona correttamente.
Cause: WEDOS Protection may preemptively block large ranges of IP addresses, for example based on bad reputation. However, between these ranges there may be unproblematic units of addresses used by plugins, templates and generally APIs that your website needs to communicate with, but cannot.
Un’altra causa frequente del problema è la restrizione dell’accesso a un’applicazione o a un’interfaccia di terze parti che in origine avevi configurato per l’IP del server Webhosting. Dopo l’attivazione di WEDOS Protection, però, vi accedi da uno dei numerosi indirizzi IP regionali del sistema.
Solution: Chiedi all’assistenza del terzo bloccato di fornire l’elenco completo degli indirizzi IP che dobbiamo inserire in whitelist da parte nostra per ripristinare la comunicazione. Devono essere pochi indirizzi specifici: grandi quantità o interi intervalli di norma sono problematici.
Once you have this list, send the following request ⧉:
Please whitelist the IP addresses (replace the parenthesis with a list of addresses) in the WEDOS Protection system in order to restore the connection of the website (replace the parenthesis with the name of your website) with the service (replace the parenthesis with the name of the template, plugin, API or other setvice that cannot connect).
Requests are usually processed by the technical department within 2 hours, depending on the department’s workload and the complexity of the request (IP address reputation verification).
If, on the other hand, the source of the problem is caused by a blocked connection on a third-party server (typically payment gateways), enable communication for IP addresses from the list at https://ips.wedos.global/ips.json ⧉ (aggiornato automaticamente).
Email Delivery
Issue: Emails sent from the website (e.g. forms) end up in spam or are not delivered at all.
Cause: The most common cause is a problem with verifying the SPF record due to a different A record of the domain and the actual IP address of the web server.
Solution: Aggiungi l’indirizzo IP effettivo del Webhosting al record SPF del dominio utilizzando il codice ip4:X.X.X.X. Trovi istruzioni dettagliate nell’articolo Emails – SPF record ⧉.
FAQ
What if the attacked Webhosting domain uses third-party DNS servers?
In this case, a technician tries to contact the owner via email and SMS. As long as we cannot effectively protect the service, we limit its parameters or shut it down completely.
How do I know that a website is using WEDOS Global?
Check the DNS A records. If you find two values 45.138.107.X, dove X is a number from 0 to 255, il dominio punta a WEDOS Protection.
For AAAA records, the corresponding value is 2a0e:acc0::X.
What if I have a different problem or your solution doesn’t work?
Chiedi all’assistenza di verificare il problema seguendo questa guida.
Why should I set up WEDOS Global when I’m already protected by another service?
We receive a large amount of unwanted traffic even from domains using other protective services. In some cases, if we cannot enable WEDOS Protection for a website under attack, we have no choice but to limit/disable web hosting.