-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration from local path fails with "migrate from '' is not allowed: unknown hostname" #14700
Comments
See: https://docs.gitea.io/en-us/config-cheat-sheet/#migrations-migrations in particular:
In the
|
I don't think this is resolved. The problem is the form |
Ok well that's slightly different from what the report initially stated. I'll reopen. |
PR go-gitea#13610 unfortunately disabled importing repositories from local paths. This PR restores this functionality. Fix go-gitea#14700 Signed-off-by: Andrew Thornton <art27@cantab.net>
I understand now! Sorry it took me so long to get what the problem was. |
…gitea#14925) Backport go-gitea#14925 PR go-gitea#13610 unfortunately disabled importing repositories from local paths. This PR restores this functionality. Fix go-gitea#14700 Signed-off-by: Andrew Thornton <art27@cantab.net>
Ubuntu 16.04.6 LTS,
Docker image gitea/gitea:1
[x]
):[loads of SQL log entries]
2021/02/16 17:35:06 modules/task/task.go:51:handle() [E] Run task failed: migrate from '' is not allowed: unknown hostname
Description
In recent gitea versions importing from local files fails with the error "modules/task/task.go:51:handle() [E] Run task failed: migrate from '' is not allowed: unknown hostname".
This appears to be an artifact of #13610 which attempts to verify IP address range even for local files.
Consequently setting
[migrations]ALLOW_LOCALNETWORKS = true
works as a fairly non-obvious workaroundThe text was updated successfully, but these errors were encountered: