потрібно налаштувати varnish cache для nginx+magento 2
на сервері знаходяться multiple domains: dev-1, dev-x + react app
ubuntu 20.04
varnish-6.2.1
nginx/1.18.0
php7.4
m2.4.5
varnishlog
* << Request >> 65543
- Begin req 65540 rxreq
- Timestamp Start: 1707940991.826304 0.000000 0.000000
- Timestamp Req: 1707940991.826304 0.000000 0.000000
- VCL_use boot
- ReqStart 90.220.150.194 59483 a0
- ReqMethod GET
- ReqURL /favicon.ico
- ReqProtocol HTTP/1.1
- ReqHeader Host: dev-x
- ReqHeader Connection: keep-alive
- ReqHeader User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
- ReqHeader Accept: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
- ReqHeader Referer: http://dev-x/
- ReqHeader Accept-Encoding: gzip, deflate
- ReqHeader Accept-Language: en-GB,en-US;q=0.9,en;q=0.8
- ReqHeader Cookie: sc=ECA62BA5-7986-36D8-AFBA-84DA22758890; _fbp=fb.2.1688507435911.52144711; _tt_enable_cookie=1; _ttp=9dTL75wgmu_TaFolqPR-4vjQwXA; _ga_JR0SDLK59D=GS1.1.1689024183.2.1.1689025576.0.0.0; s_fid=65C43C7BBE13C897-2177D09BDAF97914; apt.uid=AP-XD7ZED5OKD
- ReqHeader X-Forwarded-For: 90.220.150.194
- VCL_call RECV
- ReqHeader grace: none
- ReqURL /favicon.ico
- ReqUnset Accept-Encoding: gzip, deflate
- ReqHeader Accept-Encoding: gzip
- VCL_return hash
- VCL_call HASH
- VCL_return lookup
- VCL_call MISS
- VCL_return fetch
- Link bereq 65544 fetch
- Timestamp Fetch: 1707940991.826489 0.000185 0.000185
- RespProtocol HTTP/1.1
- RespStatus 503
- RespReason Backend fetch failed
- RespHeader Date: Wed, 14 Feb 2024 20:03:11 GMT
- RespHeader Server: Varnish
- RespHeader content-type: text/html; charset=utf-8
- RespHeader Retry-After: 5
- RespHeader X-Varnish: 65543
- RespHeader Age: 0
- RespHeader Via: 1.1 varnish (Varnish/6.2)
- VCL_call DELIVER
- RespHeader X-Magento-Cache-Debug: MISS
- RespHeader Pragma: no-cache
- RespHeader Expires: -1
- RespHeader Cache-Control: no-store, no-cache, must-revalidate, max-age=0
- RespUnset Age: 0
- RespUnset Server: Varnish
- RespUnset X-Varnish: 65543
- RespUnset Via: 1.1 varnish (Varnish/6.2)
- VCL_return deliver
- Timestamp Process: 1707940991.826502 0.000198 0.000013
- Filters
- RespHeader Content-Length: 282
- RespHeader Connection: keep-alive
- Timestamp Resp: 1707940991.826518 0.000214 0.000016
- ReqAcct 1145 0 1145 298 282 580
- End
* << Session >> 16
- Begin sess 0 HTTP/1
- SessOpen 90.220.150.194 59482 a0 54.39.18.164 80 1707940991.717022 22
- SessClose RX_TIMEOUT 5.052
- End
* << Session >> 65540
- Begin sess 0 HTTP/1
- SessOpen 90.220.150.194 59483 a0 54.39.18.164 80 1707940991.712121 21
- Link req 65541 rxreq
- Link req 65543 rxreq
- SessClose RX_TIMEOUT 5.165
- End
Budget: 4500 UAH Deadline: 1 day
Welcome, ready to perform, write in personal awareness.
Specialized in Magento
Who can help set up such a setup: I plan to deploy a server that will work in parallel with 4–5 different AI models for programming tasks. The key requirement is multi-user access: several developers will be able to use the server simultaneously, each in an isolated session with their own agents. Models Claude / GPT / Kimi k3
As part of enhancing the cybersecurity level of our infrastructure, we need to abandon the practice of storing "eternal" and static API keys, passwords, and integration tokens in the configuration files (.env, appsettings.json, config.yaml) of our microservices. Business Goal: Create a single secure storage point for confidential data (secrets) with a mechanism for their automatic updating (rotation) in external systems on a schedule. Our other services will request current tokens "on the fly" via API, which will minimize damage in case of compromise of any system component.Security Model and Encryption (Crypto Core) No secret should be stored in plaintext in the database. Upon application startup, a Master Key is passed to the environment variables. If the key is missing or has an invalid length, the service should fail at the initialization stage with a clear error in the logs. Each secret is encrypted before being written to the database using this Master Key. Upon request, it is decrypted in memory and returned in the response body.Audit Logging (Audit Trail) Any action with secrets (creation, reading by the service, successful or unsuccessful rotation) must be recorded in a separate log file audit.log (or a separate table in the database). Strict Taboo: It is strictly prohibited to record the actual values of secrets in the audit log (neither in plaintext nor in encrypted form).
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.