Skip to content

Commit 1621a7a

Browse files
kolbeckJesper KolbeckNGPixel
authored
Add help to solve 431 errors with Azure Cloud (requarks#17)
* Add help to solve 431 errors with Azure Cloud * Update azurewebapp.md Co-authored-by: Jesper Kolbeck <[email protected]> Co-authored-by: Nicolas Giard <[email protected]>
1 parent a3d2780 commit 1621a7a

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

install/azurewebapp.md

+21-1
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,24 @@ We can now create the App Service where our wiki will run.
7474
1. Browse to your app public URL. *(Can be found in the **Overview** tab of your web app resource)*
7575
1. Follow the instructions to create the admin account and start using your wiki.
7676
77-
![](https://a.icons8.com/cqaghpTd/Zi0crm/svg.svg){.align-abstopright}
77+
# 4. Troubleshooting
78+
79+
## 4.1 431 Request Header Fields Too Large Issues
80+
81+
Enabling **App Service Authentication** in **Azure** might cause `Request Header Fields Too Large` errors.
82+
To fix this:
83+
1. In your Azure Web App, navigate to **Configuration**.
84+
1. Add the following **Application Settings**:
85+
```
86+
WEBSITE_AUTH_DISABLE_IDENTITY_FLOW: true
87+
```
88+
89+
The issue can re-appear for graphql queries when enabling SAML 2.0 authentication in Wiki.js, even with above fix.
90+
To solve that we need to increase the max header size for NodeJS.
91+
1. In your Azure Web App, navigate to **Configuration**.
92+
1. Add the following **Application Settings**:
93+
```
94+
NODE_OPTIONS: --max-http-header-size=81920
95+
```
96+
97+
![](https://a.icons8.com/cqaghpTd/Zi0crm/svg.svg){.align-abstopright}

0 commit comments

Comments
 (0)