Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
1c9b324e
Commit
1c9b324e
authored
Oct 29, 2020
by
Catalin Irimie
Committed by
Mike Jang
Oct 29, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note about old git-lfs client for Geo requests
parent
2e9af7dc
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
11 additions
and
0 deletions
+11
-0
doc/administration/geo/index.md
doc/administration/geo/index.md
+1
-0
doc/administration/geo/replication/troubleshooting.md
doc/administration/geo/replication/troubleshooting.md
+10
-0
No files found.
doc/administration/geo/index.md
View file @
1c9b324e
...
...
@@ -116,6 +116,7 @@ The following are required to run Geo:
-
[
Ubuntu
](
https://ubuntu.com
)
16.04+
-
PostgreSQL 11+ with
[
Streaming Replication
](
https://wiki.postgresql.org/wiki/Streaming_Replication
)
-
Git 2.9+
-
Git-lfs 2.4.2+ on the user side when using LFS
-
All nodes must run the same GitLab version.
Additionally, check GitLab's
[
minimum requirements
](
../../install/requirements.md
)
,
...
...
doc/administration/geo/replication/troubleshooting.md
View file @
1c9b324e
...
...
@@ -782,3 +782,13 @@ To resolve this issue:
using IPv6 to send its status to the
**primary**
node. If it is, add an entry to
the
**primary**
node using IPv4 in the
`/etc/hosts`
file. Alternatively, you should
[
enable IPv6 on the **primary** node
](
https://docs.gitlab.com/omnibus/settings/nginx.html#setting-the-nginx-listen-address-or-addresses
)
.
## Fixing client errors
### Authorization errors from LFS HTTP(s) client requests
You may have problems if you're running a version of
[
Git LFS
](
https://git-lfs.github.com/
)
before 2.4.2.
As noted in
[
this authentication issue
](
https://github.com/git-lfs/git-lfs/issues/3025
)
,
requests redirected from the secondary to the primary node do not properly send the
Authorization header. This may result in either an infinite
`Authorization <-> Redirect`
loop, or Authorization errors.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment