admpub / nging Goto Github PK

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

我想参与到websocket设计部分 使用golang 谢谢

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

dmitri.shuralyov.com/app/[email protected]: unrecognized import path "dmitri.shuralyov.com/app/changes" (https fetch: Get https://dmitri.shuralyov.com/app/changes?go-get=1: EOF)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your /go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

文件：nging_linux_amd64.zip
系统：Debian 10

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

安装的时候，密码小于8位，前段无提示，点击安装没反应
--返回 数据，state=0，操作失败。运行日志里面有看到密码不能小于8位

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

请问支持反向代理内容替换吗，有参考的信息吗

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your /go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

2.1.1版本
环境：centos7
nging2.1.1+sqllite

1.修改用户密码永远报密码错误；
2.注册邀请码发送注册完毕没有挂钩上角色。

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

sourcegraph.com/sourcegraph/[email protected]: unrecognized import path "sourcegraph.com/sourcegraph/go-diff" (parse https://sourcegraph.com/sourcegraph/go-diff?go-get=1: no go-import meta tags ())

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

如题。

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

(The purpose of this report is to alert admpub/nging to the possible problems when admpub/nging try to upgrade the following dependencies)

An error will happen when upgrading library mholt/certmagic:

github.com/mholt/certmagic

-Now Moved To: caddyserver/certmagic
-Latest Version: v0.11.2 (committed 77f91b9 18 days ago)
-Where did you use it:
https://github.com/admpub/nging/search?q=%22github.com%2Fmholt%2Fcertmagic%22&unscoped_q=%22github.com%2Fmholt%2Fcertmagic%22
-Detail:

github.com/caddyserver/certmagic/go.mod

module github.com/caddyserver/certmagic
go 1.14
require (
	github.com/go-acme/lego/v3 v3.7.0
	github.com/klauspost/cpuid v1.2.3
	golang.org/x/crypto v0.0.0-20200302210943-78000ba7a073
) 

github.com/caddyserver/certmagic/acmemanager.go

package certmagic
import (
	"github.com/go-acme/lego/v3/acme"
	"github.com/go-acme/lego/v3/certificate"
	"github.com/go-acme/lego/v3/challenge"
	"github.com/go-acme/lego/v3/challenge/dns01"
	…
)

This problem was introduced since caddyserver/certmagic v0.7.0(committed 925f85a on 13 Sep 2019) . If you try to upgrade caddyserver/certmagic to version v0.7.0 and above, you will get an error--- no package exists at "github.com/go-acme/lego/v3"
NOTICE HERE The github.com/mholt/certmagic makes it very difficult for downstream module users to use admpub/nging. Force downstream module users to use vendor if they want to use admpub/nging

I investigated the libraries (caddyserver/certmagic >= v0.7.0) release information and found the root cause of this issue is that----

1. These dependencies all added Go modules in the recent versions.

2. They all comply with the specification of "Releasing Modules for v2 or higher" available in the Modules documentation. Quoting the specification:

A package that has migrated to Go Modules must include the major version in the import path to reference any v2+ modules. For example, Repo github.com/my/module migrated to Modules on version v3.x.y. Then this repo should declare its module path with MAJOR version suffix "/v3" (e.g., module github.com/my/module/v3), and its downstream project should use "github.com/my/module/v3/mypkg" to import this repo’s package.

3. This "github.com/my/module/v3/mypkg" is not the physical path. So earlier versions of Go (including those that don't have minimal module awareness) plus all tooling (like dep, glide, govendor, etc) don't have minimal module awareness as of now and therefore don't handle import paths correctly See golang/dep#1962, golang/dep#2139.

Note: creating a new branch is not required. If instead you have been previously releasing on master and would prefer to tag v3.0.0 on master, that is a viable option. (However, be aware that introducing an incompatible API change in master can cause issues for non-modules users who issue a go get -u given the go tool is not aware of semver prior to Go 1.11 or when module mode is not enabled in Go 1.11+).
Pre-existing dependency management solutions such as dep currently can have problems consuming a v2+ module created in this way. See for example dep#1962.
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Solution

1. Migrate to Go Modules.

Go Modules is the general trend of ecosystem, if you want a better upgrade package experience, migrating to Go Modules is a good choice.

Migrate to modules will be accompanied by the introduction of virtual paths(It was discussed above).

This "github.com/my/module/v3/mypkg" is not the physical path. So Go versions older than 1.9.7 and 1.10.3 plus all third-party dependency management tools (like dep, glide, govendor, etc) don't have minimal module awareness as of now and therefore don't handle import paths correctly.

Then the downstream projects might be negatively affected in their building if they are module-unaware (Go versions older than 1.9.7 and 1.10.3; Or use third-party dependency management tools, such as: Dep, glide, govendor…).

2. Maintaining v2+ libraries that use Go Modules in Vendor directories.

If admpub/nging want to keep using the dependency manage tools (like dep, glide, govendor, etc), and still want to upgrade the dependencies, can choose this fix strategy.
Manually download the dependencies into the vendor directory and do compatibility dispose(materialize the virtual path or delete the virtual part of the path). Avoid fetching the dependencies by virtual import paths. This may add some maintenance overhead compared to using modules.

As the import paths have different meanings between the projects adopting module repos and the non-module repos, materialize the virtual path is a better way to solve the issue, while ensuring compatibility with downstream module users. A textbook example provided by repo github.com/moby/moby is here:
https://github.com/moby/moby/blob/master/VENDORING.md
https://github.com/moby/moby/blob/master/vendor.conf
In the vendor directory, github.com/moby/moby adds the /vN subdirectory in the corresponding dependencies.
This will help more downstream module users to work well with your package.

Summary

You can make a choice when you meet this DM issues by balancing your own development schedules/mode against the affects on the downstream projects.

For this issue, Solution 1 can maximize your benefits and with minimal impacts to your downstream projects the ecosystem.

References

• https://github.com/golang/go/wiki/Modules#semantic-import-versioning
• https://golang.org/cmd/go/#hdr-Module_compatibility_and_semantic_versioning
• https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Do you plan to upgrade the libraries in near future?
Hope this issue report can help you ^_^
Thank you very much for your attention.

Best regards,
Kate

ssh连接提示连接出错，sftp可以正常连接。
使用的是ARM64二进制编译版本
欢迎使用 Nging v3.0.1 licensed
BUILD: 20200930210457
COMMIT: 9fdb489

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

是因为不支持么

mysql数据导出功能无效，点导出无反应。
顺便问下，可以集成mongodb数据导入导出功能么。
欢迎使用 Nging v3.0.2 licensed
BUILD: 20201023190842
COMMIT: 69dbc79

The module path github.com/mholt/certmagic found in your /go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

尝试链接启动，都不成功，不知道是不是版本不兼容服务器的frps版本
2020/01/01 09:31:11 [I] [service.go:223] login to server success, get run id [5736bce10bd09b6b], server udp port [6667]
2020/01/01 09:31:11 [I] [proxy_manager.go:137] [5736bce10bd09b6b] proxy added: [yaitoo23.ssh]
2020/01/01 09:31:11 [I] [service.go:223] login to server success, get run id [7c5a565ecd11dd15], server udp port [6667]
2020/01/01 09:31:11 [I] [proxy_manager.go:137] [7c5a565ecd11dd15] proxy added: [woshiyonghubiaos.ssh]
2020/01/01 09:31:11 [W] [control.go:207] read error: message type error
2020/01/01 09:31:11 [I] [control.go:228] control writer is closing
2020/01/01 09:31:11 [I] [service.go:129] try to reconnect to server...
2020/01/01 09:31:11 [W] [control.go:207] read error: message type error
2020/01/01 09:31:11 [I] [control.go:228] control writer is closing
2020/01/01 09:31:11 [I] [service.go:129] try to reconnect to server...

不能在服务器端管理站点吗？
在win10下布置好了，可以出现管理界面。

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

AGPL协议不是很友好，有没有打算变更为BSD/Apache2/MIT

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.

二进制下载不能访问404了

The module path github.com/mholt/certmagic found in your go.mod doesn't match the actual path github.com/caddyserver/certmagic found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/caddyserver/certmagic should resolve this issue.

View the update logs.