pg: mellium.im/sasl: unrecognized import path
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.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (3 by maintainers)
It’s not about
mellium.imitself but about shared Netlify ips - some of them are blacklisted by providers. Sometimesmellium.imis resolved with blacklisted ip.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.1in ourgo.modand it helped to eliminate the error.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.
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.
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.
If you upgrade to using Go Modules this problem goes away because it keeps a checksum files for exactly this purpose.
Not directly related, but why is the go-pg package depending on
mellium.im/saslinstead ofgithub.com/mellium/sasl? This feels like a potential security issue if mellium.im gets hijacked and redirects to something else.