Your certificate is already being transported to the pprof tool over the HTTPS connection. The problem is it's not valid for the IP address 127.0.0.1.

Ah yes that seemed to fixed it. Oddly enough browsers and test-tools accept both 127.0.0.1 and localhost locally for testing on that certificate tho.

Now I'm not getting any output tho. I'm using Gin and have _ "net/http/pprof" also imported but not seeing anything:

$ go tool pprof https://localhost:8900/debug/pprof/profile
Fetching profile from https://localhost:8900/debug/pprof/profile
Please wait... (30s)
Saved profile in /Users/erwin/pprof/pprof.localhost:8900.samples.cpu.002.pb.gz
Entering interactive mode (type "help" for commands)
(pprof) list
profile is empty
(pprof) top5
profile is empty
(pprof) top
profile is empty

Am I missing something?

My overview page show this after calling some heavier URLs (milliseconds):

/debug/pprof/

profiles:
0   block
9   goroutine
21  heap
12  threadcreate

full goroutine stack dump

I also tried running build from the CLI and it also didn't create any pprof data while running HTTP server (Gin). All my normal (non-web) Go apps profile without issues.

UPDATE

Now it shows something, but still weird results:

$ go tool pprof https://localhost:8900/debug/pprof/profile
Fetching profile from https://localhost:8900/debug/pprof/profile
Please wait... (30s)
Saved profile in /Users/erwin/pprof/pprof.localhost:8900.samples.cpu.003.pb.gz
Entering interactive mode (type "help" for commands)
(pprof) top5
9.86s of 9.86s total (  100%)
      flat  flat%   sum%        cum   cum%
     9.86s   100%   100%      9.86s   100%  
(pprof) top
9.86s of 9.86s total (  100%)
      flat  flat%   sum%        cum   cum%
     9.86s   100%   100%      9.86s   100%  
(pprof) list
Total: 9.86s
(pprof)

I'm guessing your service was idle during those 30 seconds, so there was nothing for pprof to measure.

It seems like there's no bug here, so I'm going to optimistically close. Happy to reopen if mistaken though.

If you have more questions about using Go (as opposed to suspected problems within Go itself), please see: https://github.com/golang/go/wiki/Questions

Cheers