nginx rewrite rule example in Install > Containers is broken

Open
#1,349 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
nginx
Domain
documentation

Research direction

Open the Install > Containers documentation and locate the nginx rewrite rule example. Compare it with the working configuration in the linked seamless-mode deployment example, then verify that the corrected configuration allows login without the reported backend error.

Written by the indexing model from the issue text.

Description

The nginx rewrite rule is broken. Deploying with this configuration you will not be able to login due to backend error:

 /++api++/POST_application_json_
backend_1   | Traceback (innermost last):
backend_1   |   Module ZPublisher.WSGIPublisher, line 167, in transaction_pubevents
backend_1   |   Module ZPublisher.WSGIPublisher, line 376, in publish_module
backend_1   |   Module ZPublisher.WSGIPublisher, line 271, in publish
backend_1   |   Module ZPublisher.mapply, line 85, in mapply
backend_1   |   Module ZPublisher.WSGIPublisher, line 68, in call_object
backend_1   |   Module plone.rest.service, line 22, in __call__
backend_1   |   Module plone.restapi.services, line 19, in render
backend_1   |   Module plone.restapi.services.content.add, line 41, in reply
backend_1   | zExceptions.BadRequest: Property '@type' is required

Instead, this works as expected: https://6.dev-docs.plone.org/volto/deploying/seamless-mode.html#nginx-example-config-for-seamless-mode-deployments

Dominant language
Makefile
Stars
106
Forks
190
Avg merge
3d 2h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plone/documentation

All issues in plone/documentation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.