Tried building - did not work out

systemcrash commented 1 year ago

Not straightforward, managed to build from source, with updated dnscontrol (v3.29.1), npm install, go get blah blah blah Running on darwin.

and got this:

2023/03/25 23:50:30 [Recovery] 2023/03/25 - 23:50:30 panic recovered:
runtime error: invalid memory address or nil pointer dereference
/usr/local/Cellar/go/1.20.2/libexec/src/runtime/panic.go:260 (0x104aafc)
    panicmem: panic(memoryError)
/usr/local/Cellar/go/1.20.2/libexec/src/runtime/signal_unix.go:837 (0x104aacc)
    sigpanic: panicmem()
/usr/local/Cellar/go/1.20.2/libexec/src/io/io.go:701 (0x10b3cb9)
    ReadAll: n, err := r.Read(b[len(b):cap(b)])
/usr/local/Cellar/go/1.20.2/libexec/src/io/ioutil/ioutil.go:27 (0x160073c)
    ReadAll: return io.ReadAll(r)
/Users/mofo/git/happydomain/ui/routes.go:109 (0x160071c)
    serveOrReverse.func2: v, _ := ioutil.ReadAll(f)
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/context.go:174 (0x15f2ae1)
    (*Context).Next: c.handlers[c.index](c)
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/recovery.go:102 (0x15f2acc)
    CustomRecoveryWithWriter.func1: c.Next()
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/context.go:174 (0x15f1c06)
    (*Context).Next: c.handlers[c.index](c)
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/logger.go:240 (0x15f1be9)
    LoggerWithConfig.func1: c.Next()
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/context.go:174 (0x15f0c8a)
    (*Context).Next: c.handlers[c.index](c)
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/gin.go:620 (0x15f0911)
    (*Engine).handleHTTPRequest: c.Next()
/Users/mofo/go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/gin.go:576 (0x15f043c)
    (*Engine).ServeHTTP: engine.handleHTTPRequest(c)
/usr/local/Cellar/go/1.20.2/libexec/src/net/http/server.go:2936 (0x13e3955)
    serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/usr/local/Cellar/go/1.20.2/libexec/src/net/http/server.go:1995 (0x13dee71)
    (*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/usr/local/Cellar/go/1.20.2/libexec/src/runtime/asm_amd64.s:1598 (0x1067ea0)
    goexit: BYTE    $0x90   // NOP

I give up.

systemcrash commented 1 year ago

Also got this, so commented it out.

# git.happydns.org/happydomain/providers
providers/providers.go:124:70: undefined: providers.CanUseOPENPGPKEY

If I run on this git

git log -S providers.CanUseOPENPGPKEY  --source --all
commit 26933d5917a0f650ca451ba6b7db9667b03c77eb

but if I run on dnscontrol git

git log -S CanUseOPENPGPKEY  --source --all

...nothing.

WAT?

When I attempt to visit your specific git, no browser likes you:

Firefox detected a potential security threat and did not continue to git.happydns.org because this website requires a secure connection.

What can you do about it?

git.happydns.org has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.

Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for git.happydns.org. The certificate is only valid for jizah.masr.nemunai.re.

Error code: SSL_ERROR_BAD_CERT_DOMAIN

git doesn't like you either.

Come on. HTTPS Certificates are free.

And if this is something custom that you added, make a PR and contribute it to dnscontrol, maybe?

systemcrash commented 1 year ago

Same problem on get

Did Not Connect: Potential Security Issue

Firefox detected a potential security threat and did not continue to get.happydomain.org because this website requires a secure connection.

What can you do about it?

get.happydomain.org has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.

Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for get.happydomain.org. The certificate is only valid for jizah.masr.nemunai.re.

Error code: SSL_ERROR_BAD_CERT_DOMAIN

nemunaire commented 1 year ago

Hi @systemcrash!

Sorry for not being actively involved recently, I'm personally really busy while preparing a huge event for another project.

We had an incident last week on our secondary server and it lacked automation rules to redeploy the config in no time. git/get/help are now back online (and with automation)!

Regarding the update of dnscontrol, you need to know that we use a fork of dnscontrol, hosted here: https://github.com/happyDomain/dnscontrol/tree/happydns as there are 3 modifications not currently suitable for upstream merge.

I delayed the update of dnscontrol as there were no important thing apart the new diff tool, that requires to be tested extensively on our side.

If you want to give it a try, I just update the branch. You can update the version in go.mod (the replace at the bottom) to 3.29.11 (to make go vendor happy, I create fake versions in our repository 3.X.Y, with Y+10).

systemcrash commented 1 year ago

Ah, well, happy landings at your event.

What is your automation tool BTW?

nemunaire commented 1 year ago

We are working on Ansible support currently.

nemunaire commented 1 year ago

Things should be back to normal: dnscontrol is up-to-date, including your OPENPGPKEY work instead of mine.

Let us know if you have build issues again!

happyDomain / happydomain

Tried building - did not work out #16