You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about-hypernode/support/what-to-expect-from-hipex-support.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Please use [support@hipex.io](mailto:support@hipex.io) for all your questions/pr
13
13
14
14
15
15
## Can I reach Hipex by phone?
16
-
Yes, you can during office hours you can call us at +31(0)85-888 77 54.
16
+
Yes, you can during office hours you can call us at +31(0)85-888 77 54.
17
17
18
18
# Outside office hours
19
19
It's after business hours and I have an emergency, what should I do?
@@ -23,13 +23,13 @@ An urgent matter is for example:
23
23
- customers can't place any orders
24
24
25
25
26
-
## Step 1 Use your mail that is known in Pack and send us a ticket to spoed@hipex.io
26
+
## Step 1 Use your mail that is known in Pack and send us a ticket to spoed@hipex.io
27
27
Don't forget to mention:
28
28
29
29
- name of the server or your domain
30
30
- an extensive description of your problem
31
31
32
-
Please know if you don't use the correct mail adress, your ticket won't be follow up as the system doesn't recogonize.
32
+
Please know if you don't use the correct mail adress, your ticket won't be follow up as the system doesn't recogonize.
33
33
34
34
## Step 2 The Request is Sent to the On Duty Hero
35
35
As soon as you report the disruption via one of the designated channels, an alert is sent via PagerDuty to the HERO (Hypernode/Hipex Emergency Request Operative) team. One of our heroes will confirm receipt of the urgent ticket.
@@ -46,4 +46,3 @@ Upon resolving the issue, the Hero will issue a debrief to the Support Departmen
46
46
47
47
# Hipex knowledge base
48
48
Till further notice [Hipex knowledge base](https://www.hipex.io/docs/nl/) will exist. Eventually we will integrate both Hypernode and [Hipex knowledge base](https://www.hipex.io/docs/nl/) together.
Customers with Hypernode Pelican, Falcon (formerly known as Professional) and Eagle (formerly known as Excellence plans can use Varnish to boost their Magento shop. This article explains how you can configure Varnish 4 or 6 for your Hypernode. If you want to know which Varnish version you need to configure, please check the [Magento documentation](https://devdocs.magento.com/guides/v2.4/install-gde/system-requirements.html) first. Do you have a Magento 1 shop, please check [this article](https://support.hypernode.com/knowledgebase/varnish-on-magento1/).
5
6
6
7
Although Varnish is extremely awesome when it get's to speeding up websites, Varnish is a complex technique that needs some experience to set it up. Don't implement varnish on production nodes without testing Varnish first on a [development node](https://support.hypernode.com/knowledgebase/development-plans-for-your-magento-shop/) or the [Hypernode Docker](https://support.hypernode.com/en/best-practices/testing/hypernode-docker).
7
8
8
-
9
-
Enable Varnish 4.0 or 6.0 for Magento 2.x
10
-
-----------------------------------------
9
+
## Enable Varnish 4.0 or 6.0 for Magento 2.x
11
10
12
11
As Magento 2 supports Varnish out of the box, there is no need for the turpentine extension anymore in Magento 2. Simply follow the steps below to configure Varnish 4.0 or 6.0 for Magento 2.
**Enable Varnish via the [Service Panel](https://service.byte.nl/)**
32
32
33
-
* Log in on the Service Panel
34
-
* Go to the tab "Instellingen"
35
-
* Click on "Varnish"
36
-
* Use the switch to enable Varnish
33
+
- Log in on the Service Panel
34
+
- Go to the tab "Instellingen"
35
+
- Click on "Varnish"
36
+
- Use the switch to enable Varnish
37
37
38
38
**Enable Varnish via the [Control Panel](https://auth.hypernode.com/)**
39
39
40
-
* Click on "Hypernodes"
41
-
* Click on "Caching"
42
-
* Select the Hypernode
43
-
* Click on "Enable Varnish"
40
+
- Click on "Hypernodes"
41
+
- Click on "Caching"
42
+
- Select the Hypernode
43
+
- Click on "Enable Varnish"
44
44
45
-
Configure Varnish on the Vhost
46
-
------------------------------
45
+
## Configure Varnish on the Vhost
47
46
48
-
Since the introduction of **[hypernode-manage-vhosts](https://changelog.hypernode.com/changelog/release-7166-hypernode-manage-vhosts-enabled-by-default/)**Hypernode may work somewhat different than you might be used to. With HMV enabled, it requires one more step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command:
47
+
Since the introduction of \*\*[hypernode-manage-vhosts](https://changelog.hypernode.com/changelog/release-7166-hypernode-manage-vhosts-enabled-by-default/)\*\*Hypernode may work somewhat different than you might be used to. With HMV enabled, it requires one more step to configure Varnish for your shop/vhost. Remember, for each domain, there should be a vhost created. You can list an overview of all configured vhosts with `hypernode-manage-vhosts --list`. While you do that, note that there is a column, "varnish". By default this is set to "False". Which means that Varnish isn't configured for this vhost. You can configure Varnish for the vhost by running the following command:
49
48
50
49
```console
51
50
$ hypernode-manage-vhosts EXAMPLE.COM --varnish
52
51
```
53
52
54
-
Configure Magento 2.x for Varnish
55
-
---------------------------------
53
+
## Configure Magento 2.x for Varnish
56
54
57
-
* Log in to the Magento Admin/Backend as an administrator.
58
-
* Navigate to **Stores > Configuration > Advanced > System > Full Page Cache**
59
-
* From the **Caching Application** list, click `Varnish Caching`
60
-
* Enter a TTL value
61
-
* Expand Varnish Configuration and insert the correct information:
62
-
+ `Backend Host`: 127.0.0.1
63
-
+ `Backend Port`: 8080
64
-
* Save your VCL by clicking the button **`Save config`** in the top right
65
-
* Click *Export VCL for Varnish 4 or *Export VCL for Varnish 6**
55
+
- Log in to the Magento Admin/Backend as an administrator.
56
+
- Navigate to **Stores > Configuration > Advanced > System > Full Page Cache**
57
+
- From the **Caching Application** list, click `Varnish Caching`
58
+
- Enter a TTL value
59
+
- Expand Varnish Configuration and insert the correct information:
60
+
-`Backend Host`: 127.0.0.1
61
+
-`Backend Port`: 8080
62
+
- Save your VCL by clicking the button **`Save config`** in the top right
63
+
- Click *Export VCL for Varnish 4 or *Export VCL for Varnish 6**
66
64
67
65
### Configure Your Backend Servers Through the Commandline
68
66
@@ -112,15 +110,15 @@ backend default {
112
110
113
111
Make sure you change this to the aforementioned configuration (without the health_check probe), since this will break on our Nginx configuration and will therefore result in a `503 Guru Meditation` error.
114
112
115
-
Import Your VCL into the Varnish Daemon
116
-
---------------------------------------
113
+
## Import Your VCL into the Varnish Daemon
117
114
118
115
Import your VCL into Varnish and save as `mag2`:
119
116
120
117
```console
121
118
$ varnishadm vcl.load mag2 /data/web/default.vcl
122
119
123
120
```
121
+
124
122
The output should say: *your VCL is compiled*. If you receive a `Permission denied` error, and have recently activated Varnish, please close all ssh sessions, and log back in to reload your new permissions.
125
123
126
124
Now tell Varnish to activate the loaded VCL:
@@ -129,6 +127,7 @@ Now tell Varnish to activate the loaded VCL:
129
127
$ varnishadm vcl.use mag2
130
128
131
129
```
130
+
132
131
In the examples we used the name ‘mag2’ for our VCL, but you can use any name you prefer.
133
132
134
133
### Test if the Correct VCL is Uploaded
@@ -138,16 +137,16 @@ List all VCL’s with the following command:
138
137
```console
139
138
$ varnishadm vcl.list
140
139
```
140
+
141
141
The VCL you just imported and activated should have the status `active`. If all went well, varnish is now functioning with a working VCL.
142
142
143
143
### The "Boot" profile
144
144
145
-
To make sure your .vcl stays active even after a restart of Varnish we run a script every 5 minutes which saves the running config to /data/var/varnish/default.vcl which will be used once Varnish restarts. the "boot" profile will check what the last running .vcl was, and use that config in the "boot" profile.
145
+
To make sure your .vcl stays active even after a restart of Varnish we run a script every 5 minutes which saves the running config to /data/var/varnish/default.vcl which will be used once Varnish restarts. the "boot" profile will check what the last running .vcl was, and use that config in the "boot" profile.
146
146
147
147
This will mean that your loaded .vcl profile won't be existing the next time you'll look, and that your own .vcl profile is renamed to "boot". This is expected behaviour.
148
148
149
-
Flush Your Varnish Cache When Using Magento 2
150
-
---------------------------------------------
149
+
## Flush Your Varnish Cache When Using Magento 2
151
150
152
151
To flush the Varnish cache of your Magento store on the command line you can use `/data/web/magento2/bin/magento cache:flush full_page` This will purge the Varnish cache of the local Varnish instance.
153
152
@@ -156,18 +155,18 @@ Additionally you can flush your cache through the Magento admin backend or use `
156
155
```console
157
156
$ varnishadm "ban req.url ~ ."
158
157
```
158
+
159
159
Or if you want to flush the cache for a single domain in a multisite setup:
160
160
161
161
```console
162
162
$ varnishadm "ban req.http.host == example.com"
163
163
```
164
-
Warming Your Cache
165
-
------------------
164
+
165
+
## Warming Your Cache
166
166
167
167
Magento 2 doesn't need to use turpentine anymore, so we can't use the cache crawler provided with turpentine. As an alternative you can use an extension to warm your cache or the cache warmers we provided on our Github account, [here](https://gist.github.com/hn-support/60016f4b7986ad2cce693bdf2f3501b4) and [here](https://gist.github.com/hn-support/bc7cc401e3603a848a4dec4b18f3a78d).
168
168
169
-
Enable Debug Headers
170
-
--------------------
169
+
## Enable Debug Headers
171
170
172
171
If you are implementing Varnish on Magento 2, you might want to view some caching headers that indicate whether the page is cacheable or not. To do this, put your Magento install in `Developer mode`. Now if you request a page through curl, you can see the `X-Magento-Cache-Debug` header:
In our experience the by default generated .vcl from your Magento backend often doesn't work very well. You can check this for example by running `varnishhist`, this will show you a graph with the HITS, (`|`) and MISSES (`#`). So if you're seeing a lot of MISSES (`#`) you could use **[this .vcl](https://gist.github.com/hn-support/f4d29af73d76d0f7879a2fa9d10d8411)**. We found out that this .vcl is often performing quite well.
187
+
In our experience the by default generated .vcl from your Magento backend often doesn't work very well. You can check this for example by running `varnishhist`, this will show you a graph with the HITS, (`|`) and MISSES (`#`). So if you're seeing a lot of MISSES (`#`) you could use **[this .vcl](https://gist.github.com/hn-support/f4d29af73d76d0f7879a2fa9d10d8411)**. We found out that this .vcl is often performing quite well.
190
188
191
-
****please note that this is just another standard .vcl, if this doesn't work either or you have specific requirements you should contact a Varnish implementation specialist.**
189
+
\*\***please note that this is just another standard .vcl, if this doesn't work either or you have specific requirements you should contact a Varnish implementation specialist.**
192
190
193
-
Troubleshooting
194
-
---------------
191
+
## Troubleshooting
195
192
196
193
- If you are receiving `Permission denied` errors while running `varnishadm` or other Varnish CLI commands, and you have just activated Varnish, close any existing ssh sessions, and log back in to reload your updated permissions.
197
194
- If your Varnish setup is not working over SSL, check [this article](https://support.hypernode.com/en/hypernode/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-byte-nl#Redirecting-to-HTTPS-When-Using-Varnish)
@@ -214,8 +211,8 @@ proxy_busy_buffers_size 256k;
214
211
215
212
### 503 Errors
216
213
217
-
* There is a bug when Varnish is activated on Magento 2.2.0, resulting in a "503 backend fetch" error. Please see Magento Github issue [10165](https://github.com/magento/magento2/issues/10165). For now, we advise you to either wait with upgrading to Magento 2.2.0 when using Varnish until this bug is fixed or use an adjusted .vcl as a temporary workaround:
218
-
* In Magento 2.4.x (and possibly earlier versions as well) a solution could be to disable the **product_identities_extender** plugin. This is a default Magento plugin which doesn't seem to work properly with Varnish enabled. All credit for this solution goes to [Tree of Information](https://www.treeofinformation.nl/) whom have spend a long time investigting this issue.
214
+
- There is a bug when Varnish is activated on Magento 2.2.0, resulting in a "503 backend fetch" error. Please see Magento Github issue [10165](https://github.com/magento/magento2/issues/10165). For now, we advise you to either wait with upgrading to Magento 2.2.0 when using Varnish until this bug is fixed or use an adjusted .vcl as a temporary workaround:
215
+
- In Magento 2.4.x (and possibly earlier versions as well) a solution could be to disable the **product_identities_extender** plugin. This is a default Magento plugin which doesn't seem to work properly with Varnish enabled. All credit for this solution goes to [Tree of Information](https://www.treeofinformation.nl/) whom have spend a long time investigting this issue.
0 commit comments