mellium.im/sasl: unrecognized import path

[niski84]

go get -u github.com/go-pg/pg
package mellium.im/sasl: unrecognized import path "mellium.im/sasl" (https fetch: Get https://mellium.im/sasl?go-get=1: read tcp 10.10.49.76:63173->198.199.66.189:443: wsarecv: An existing connection was forcibly closed by the remote host.)

This repository has been deleted
Our apologies, but the repository "mellium/sasl" has been deleted.

It now lives at https://github.com/mellium/sasl.

[vmihailenco]

Let's see how https://github.com/mellium/sasl/issues/3 is resolved. Code still uses old import path https://github.com/mellium/sasl/blob/master/doc.go#L15

[tangtony]

Not directly related, but why is the go-pg package depending on mellium.im/sasl instead of github.com/mellium/sasl? This feels like a potential security issue if mellium.im gets hijacked and redirects to something else.

[vmihailenco]

https://github.com/mellium/sasl/blob/master/doc.go#L15 says it must be imported as mellium.im/sasl. Can't do anything about it except vendoring the whole package.

[vmihailenco]

go get -u mellium.im/sasl works fine for me. Closing.

[SamWhited]

This should have been fixed now; sorry for the problem. Feel free to ping me if this happens again in the future; I moved everything over to Netlify, so it sholudn't be a problem anymore.

Not directly related, but why is the go-pg package depending on mellium.im/sasl instead of github.com/mellium/sasl? This feels like a potential security issue if mellium.im gets hijacked and redirects to something else.

If you upgrade to using Go Modules this problem goes away because it keeps a checksum files for exactly this purpose.

[SamWhited]

Someone posted that they were still having the problem, but the comment now appears to have been deleted. If anyone is still seeing this, can you run a traceroute and see if you have problems accessing netlify? I don't think it's going down, but maybe they block certain countries or something. If so, email me or send me a line on any Jabber compatible messenger service and I'll see what I can do about moving the repo or redirect hosting as necessary.

[cujo]

That was my post and yes, some Netlify IPs blocked by my provider was the reason. Switched to another one and problem is gone. Sorry for bothering.

[massanchik]

Still getting this

[SamWhited]

@massanchik still working fine for me; can you narrow down what the exact problem is? Is it DNS, or is the DNS lookup completing and then a route to Netlify is broken with you provider?

[massanchik]

unrecognized import path "mellium.im/sasl"

after go get -u mellium.im/sasl it works now, but shoud't it load with pg package?

[avsima]

We got this error every second case in our CI.
So I placed replace mellium.im/sasl v0.2.1 => github.com/mellium/sasl v0.2.1 in our go.mod and it helped to eliminate the error.

[SamWhited]

That's odd, I was always under the impression that Netlify was a reliable host. If anyone could actually find out what the error is (maybe by doing a dig or a traceroute to see if it's DNS or a failure to contact the host) I'd appreciate it.
If I can figure out what the actual problem is I can move to a different host or make some changes to the DNS setup.

[jh125486]

mellium.im is blocked by many proxies as it is flagged as it is a "Site known to distribute malicious software".

Since the go.mod file @ https://github.com/mellium/sasl has module mellium.im/sasl, I'm not exactly sure how to even fix this.

[SamWhited]

@jh125486 I'm not really sure what that means; can you point me to something that is blocking it with that error? We don't even serve ads on the little static site, so I can't imagine how that would come up. Of course, if there were something I'd want to know about it and fix it, but I don't see any suspicious activity on our Netlify.

What do you mean by "many proxies" too? What kind of proxies are these and how many are there?

[cujo]

It's not about mellium.im itself but about shared Netlify ips - some of them are blacklisted by providers. Sometimes mellium.im is resolved with blacklisted ip.

[SamWhited]

I see, thanks. That's a good reason to move off of Netlify and back to something where I can get my own IP (although also whatever those proxies are need to learn how the internet works and stop doing IP ranking, so maybe I'll leave it alone). I'll look into it. Suggestions welcome (feel free to email me or hit me up on Jabber so we don't clutter up this issue with noise, see my profile for my email/JID).