Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alertmanager configuration pages in docs returns "Not Found" #3483

Closed
LillyWu opened this Issue Nov 16, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@LillyWu
Copy link

LillyWu commented Nov 16, 2017

What did you do?
Check alertmanager configuration page

What did you expect to see?
The page

What did you see instead? Under which circumstances?
Page Not Found
https://prometheus.io/docs/alerting/configuration/

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Nov 16, 2017

It seems there was a blip in our docs build. It should be available again.

@grobie grobie closed this Nov 16, 2017

@LillyWu

This comment has been minimized.

Copy link
Author

LillyWu commented Nov 16, 2017

@grobie Not yet, please help investigate

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Nov 16, 2017

@LillyWu What's the output of curl -v https://prometheus.io/docs/alerting/configuration/ >/dev/null.

@gouthamve

This comment has been minimized.

Copy link
Member

gouthamve commented Nov 16, 2017

@grobie Can confirm still 404ing for me. I think its some CDN sync issue with some regions or something.

➜  ~ curl -v https://prometheus.io/docs/alerting/configuration/ >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 104.24.121.60...
* TCP_NODELAY set
*   Trying 2400:cb00:2048:1::6818:783c...
* TCP_NODELAY set
* Immediate connect fail for 2400:cb00:2048:1::6818:783c: Network is unreachable
*   Trying 2400:cb00:2048:1::6818:793c...
* TCP_NODELAY set
* Immediate connect fail for 2400:cb00:2048:1::6818:793c: Network is unreachable
* Connected to prometheus.io (104.24.121.60) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: none
  CApath: none
* loaded libnssckbi.so
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0* ALPN, server accepted to use h2
* SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* 	subject: CN=sni194015.cloudflaressl.com,OU=PositiveSSL Multi-Domain,OU=Domain Control Validated
* 	start date: Nov 05 00:00:00 2017 GMT
* 	expire date: May 14 23:59:59 2018 GMT
* 	common name: sni194015.cloudflaressl.com
* 	issuer: CN=COMODO ECC Domain Validation Secure Server CA 2,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55b7b1a16010)
> GET /docs/alerting/configuration/ HTTP/2
> Host: prometheus.io
> User-Agent: curl/7.53.1
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404 
< date: Thu, 16 Nov 2017 11:01:19 GMT
< content-type: text/html; charset=utf-8
< set-cookie: __cfduid=d0ebd8222562f3c851c332d177632357c1510830078; expires=Fri, 16-Nov-18 11:01:18 GMT; path=/; domain=.prometheus.io; HttpOnly
< cache-control: public, max-age=0, must-revalidate
< age: 2328
< vary: Accept-Encoding
< strict-transport-security: max-age=2592000; preload
< x-content-type-options: nosniff
< server: cloudflare-nginx
< cf-ray: 3be9f3993fa21389-LHR
< 
{ [1084 bytes data]
100  1866    0  1866    0     0   1032      0 --:--:--  0:00:01 --:--:--  1033
* Connection #0 to host prometheus.io left intact
@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.