6 ms·

Right now, GitLab Pages is hosted on the same servers as GitLab.com, so it gets the same attention from our engineers in terms of reliability and uptime. We're

Right now, GitLab Pages is hosted on the same servers as GitLab.com, so it gets the same attention from our engineers in terms of reliability and uptime. We're not using a global CDN, but this is something we will explore.

sytse 11y ago
We're working on adding Cloudflare in front of GitLab Pages in https://gitlab.com/gitlab-com/operations/issues/75 https://gitlab.com/gitlab-com/operations/issues/75 We don't have a lot of experience yet with DDOS protection so there might be downtime as we learn that. As you can see in the issue we're working to implement protection before we need it but it might not be ready in time nor can it protect against everything.
- deleted 11y ago
  [deleted]
- mynewtb 11y ago
  Please do not use Cloudflare. Their 'protection' against privacy aware Tor users makes accessing sites through incredibly painful.
  - iancarroll 11y ago
    GitLab can just disable that...
    - sytse 11y ago
      Good idea, I made a note in https://gitlab.com/gitlab-com/operations/issues/75#note_4599684 https://gitlab.com/gitlab-com/operations/issues/75#note_4599...
  - the_mitsuhiko 11y ago
    For what it's worth Cloudflare does not do anything different for Tor than for regular IPs. Since those are static pages with most likely not exactly questionable content the use of Tor is probably not all that important anyways that the total number of users that might be affected would be miniscule.
    - dublinben 11y ago
      >the use of Tor is probably not all that important anyways Who are you to decide that my use of Tor is not important enough?
      - sneak 11y ago
        A site operator. It isn't censorship for someone to decide who they want to talk to. CF is simply giving site owners levers to use if they so choose. While I am a strong supporter of Tor, privacy, and anonymity, CF has done nothing wrong here by allowing site operators to selectively choose who they wish to serve to.
        parallelist 11y ago
        Sounds a lot like censorship to me. It's discrimination at the very least.
        ferbivore 11y ago
        Spam filters are discrimination, but I don't see anyone suggesting we stop using those.
        erikrothoff 11y ago
        Then go after the site owners who choose to enable this.
        corobo 11y ago
        Isn't the problem along the line of so many different people using effectively the same IP addresses (exit points) and looking somewhat similar to each other? I'd imagine if there was a major ISP network out there that was doing NATing or similar for their customers so everyone came from a small set of IP addresses they'd get the same treatment. More users on the same IP means more abuse from that IP. If anything Cloudflare isn't discriminating. To handle Tor users better you'd have to discriminate (technical definition, not the negative form) to handle Tor users better
      - 11y ago
  - eknkc 11y ago
    I'm not sure what they are supposed to do if exit node ips have bad reputation.
  - tombrossman 11y ago
    I'll second this to amplify the message to please not add CloudFlare for all custom domains and if you feel you must add it then at least make it optional. This would be an absolute showstopper bug which would prevent some of us from using GitLab Pages if it became a requirement. Definitely do not want.
  - mullingitover 11y ago
    In all fairness, Tor is something of a cesspool and cloudflare is doing the best they can[1]. [1] https://blog.cloudflare.com/the-trouble-with-tor/ https://blog.cloudflare.com/the-trouble-with-tor/
    - mynewtb 11y ago
      Please consider https://blog.torproject.org/blog/trouble-cloudflare https://blog.torproject.org/blog/trouble-cloudflare
  - mullingitover 11y ago
    In all fairness, Tor is something of a cesspool and cloudflare is doing the best they can[1]. [1] https://blog.cloudflare.com/the-trouble-with-tor/ https://blog.cloudflare.com/the-trouble-with-tor/

sytse 11y ago

We're working on adding Cloudflare in front of GitLab Pages in https://gitlab.com/gitlab-com/operations/issues/75 https://gitlab.com/gitlab-com/operations/issues/75 We don't have a lot of experience yet with DDOS protection so there might be downtime as we learn that. As you can see in the issue we're working to implement protection before we need it but it might not be ready in time nor can it protect against everything.

deleted 11y ago
[deleted]
mynewtb 11y ago
Please do not use Cloudflare. Their 'protection' against privacy aware Tor users makes accessing sites through incredibly painful.
- iancarroll 11y ago
  GitLab can just disable that...
  - sytse 11y ago
    Good idea, I made a note in https://gitlab.com/gitlab-com/operations/issues/75#note_4599684 https://gitlab.com/gitlab-com/operations/issues/75#note_4599...
- the_mitsuhiko 11y ago
  For what it's worth Cloudflare does not do anything different for Tor than for regular IPs. Since those are static pages with most likely not exactly questionable content the use of Tor is probably not all that important anyways that the total number of users that might be affected would be miniscule.
  - dublinben 11y ago
    >the use of Tor is probably not all that important anyways Who are you to decide that my use of Tor is not important enough?
    - sneak 11y ago
      A site operator. It isn't censorship for someone to decide who they want to talk to. CF is simply giving site owners levers to use if they so choose. While I am a strong supporter of Tor, privacy, and anonymity, CF has done nothing wrong here by allowing site operators to selectively choose who they wish to serve to.
      - parallelist 11y ago
        Sounds a lot like censorship to me. It's discrimination at the very least.
        ferbivore 11y ago
        Spam filters are discrimination, but I don't see anyone suggesting we stop using those.
        erikrothoff 11y ago
        Then go after the site owners who choose to enable this.
        corobo 11y ago
        Isn't the problem along the line of so many different people using effectively the same IP addresses (exit points) and looking somewhat similar to each other? I'd imagine if there was a major ISP network out there that was doing NATing or similar for their customers so everyone came from a small set of IP addresses they'd get the same treatment. More users on the same IP means more abuse from that IP. If anything Cloudflare isn't discriminating. To handle Tor users better you'd have to discriminate (technical definition, not the negative form) to handle Tor users better
    - 11y ago
- eknkc 11y ago
  I'm not sure what they are supposed to do if exit node ips have bad reputation.
- tombrossman 11y ago
  I'll second this to amplify the message to please not add CloudFlare for all custom domains and if you feel you must add it then at least make it optional. This would be an absolute showstopper bug which would prevent some of us from using GitLab Pages if it became a requirement. Definitely do not want.
- mullingitover 11y ago
  In all fairness, Tor is something of a cesspool and cloudflare is doing the best they can[1]. [1] https://blog.cloudflare.com/the-trouble-with-tor/ https://blog.cloudflare.com/the-trouble-with-tor/
  - mynewtb 11y ago
    Please consider https://blog.torproject.org/blog/trouble-cloudflare https://blog.torproject.org/blog/trouble-cloudflare
- mullingitover 11y ago
  In all fairness, Tor is something of a cesspool and cloudflare is doing the best they can[1]. [1] https://blog.cloudflare.com/the-trouble-with-tor/ https://blog.cloudflare.com/the-trouble-with-tor/