Update faqs.md

content/en/docs/install/faqs.md

@@ -91,13 +91,6 @@ drive, and use the drive URL for the uploaded file as the custom icon
 URL. But, if you have configured S3 storage on a subdomain, this will still
 not fix the problem.
 
-The next easiest fix is to use your instance to proxy the image, using
-a URL like
-`https://example.com/proxy/?url=https:/files.example.com/path/to/image.png`
-(of course, replace the first `example.com` with your instance's host
-name, and the value after `?url=` with the actual URL of the custom
-icon)
-
 The "correct" fix would be for the server that's hosting the icon to
 provide CORS headers that tell browsers that the instance's domain is
 allowed to use the icon. [MDN has some examples showing how to do