-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
New remote datasets are not registered inside proxy allowed hosts when GeoNode runs asynchoronously #12828
Comments
mattiagiupponi
added a commit
that referenced
this issue
Jan 16, 2025
…lowed hosts when GeoNode runs asynchoronously
13 tasks
mattiagiupponi
added a commit
that referenced
this issue
Jan 17, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 17, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 20, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 20, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi
added a commit
that referenced
this issue
Jan 24, 2025
…lowed hosts when GeoNode runs asynchoronously
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The link post save signal should register new remote datasets (3dtiles) inside the proxy allowed hosts registry.
This works fine when run sync but fails when run asynchronously. A restart of the GeoNode instance is required for the registry to pick up the new Link URLs.
Something is wrong here probably due to the async process still running.
The text was updated successfully, but these errors were encountered: