---
url: https://next.zammad.org/it/reference/proxy-connections.md
---

# Proxy and connections

## Proxy

Questa sezione copre la configurazione del proxy tramite variabili
d'ambiente. In alternativa,

|                                             | Configurazione GUI | Variabile d'ambiente

Le seguenti variabili d'ambiente possono essere usate per configurare le
impostazioni proxy. Regola il valore.

`HTTP_PROXY`
: Variabile per il traffico HTTP. Impostala sull'indirizzo del tuo server proxy, incl.

```sh
export HTTP_PROXY="http://127.0.0.1:8080"
```

`HTTPS_PROXY`
: Variabile per il traffico HTTPS. Impostala sull'indirizzo del tuo server proxy, in.

```sh
export HTTPS_PROXY="http://127.0.0.1:8080"
```

`NO_PROXY`
: Variabile per gli indirizzi a cui accedere direttamente e senza proxy. Es.

```sh
export NO_PROXY="localhost,127.0.0.1,.example.com"
```

`ES_JAVA_OPTS`
: Variabile per impostare un proxy per Elasticsearch. Per impostazione predefinita, Elasticsearch non comunica con sistemi esterni
durante il funzionamento. Tuttavia, possono esserci casi in cui ciò è necessario. Esempio:

```sh
export ES_JAVA_OPTS="-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8080 -Dhttps.proxyHost=
```

::: tip
A seconda del tuo ambiente, potresti voler usare le varianti minuscole delle variabili.

:::

## External connections

Durante l'installazione e il funzionamento di Zammad, sono necessarie alcune
connessioni a servizi online.

| \[Address]                                        | Comment                                               |
|------------------------------|-------------------------------------------------------|
| dl.packager.io               | Download del pacchetto OS (installazione del pacchetto) |
| go.packager.io               | Come sopra; nuovo servizio di hosting dei pacchetti     |
| geo.zammad.com               | Utilizzato per i dati geografici                        |
| google.com                   | Download dei giorni festivi per il calendario           |
| index.rubygems.org           | Download delle gem per Ruby                             |
| registry.npmjs.org           | Download delle dipendenze JS                            |

Puoi usare uno script per controllare lo stato di connessione del tuo
sistema. Cerca di connettersi a.

**Recupera lo script da remoto:**

```sh
curl -fsSL https://raw.githubusercontent.com/zammad/zammad/refs/heads/stable/contrib/packa
```

**Usa lo script locale:**

```sh
/opt/zammad/contrib/packager.io/test_download_dependencies_connection.sh
```

## Web push notifications

Zammad can notify agents about their tickets on mobile devices. These
notifications are delivered as web push messages of the device's browser. On
Android, a supported browser and the installed mobile view can both receive
them. On iPhone and iPad, the mobile view has to be added to the home screen
first. How to set them up on a device is described in the [mobile view
documentation](/en/documentation/use/guides/mobile-view).

The messages are sent by the background worker of Zammad over HTTPS (port
443\) to the push service of the browser vendor. A firewall that restricts
outgoing traffic has to allow the following addresses, including their
subdomains:

| Address                     | Comment                                               |
|-----------------------------|-------------------------------------------------------|
| fcm.googleapis.com          | Web push for Chrome and other Chromium-based browsers |
| jmt17.google.com            | Alternative address of the Google push service        |
| notify.windows.com          | Web push for Microsoft Edge                           |
| push.services.mozilla.com   | Web push for Mozilla Firefox                          |
| web.push.apple.com          | Web push for Safari on iPhone, iPad and Mac           |

The proxy configuration described above applies to these connections as
well, including the no-proxy list of the GUI configuration and the
`NO_PROXY` environment variable.

Zammad only accepts device subscriptions of the push services listed
above. A browser that uses another push service cannot enable push
notifications.

There is nothing to configure in Zammad. The key pair used to sign the
messages (VAPID) is generated once per installation and is not meant to be
changed: all existing device subscriptions become invalid if it changes.

The push service of the browser vendor delivers the messages, not
Zammad. Depending on the device, delivery can take a while, for example when
battery optimization delays it on Android devices. A message that cannot be
delivered right away is kept by the push service for up to one day. On
iPhone and iPad, several messages about the same ticket stay as separate
notifications, while other platforms replace the previous one.