Skip to content

Commit bfb64b6

Browse files
authored
DOC: Updated Troubleshooting Guide (#1315)
* updated troubleshooting steps * updated troubleshooting steps * added cluster update troubleshooting in docs * updated content
1 parent 9c58351 commit bfb64b6

File tree

1 file changed

+52
-1
lines changed

1 file changed

+52
-1
lines changed

docs/FAQs/devtron-troubleshoot.md

Lines changed: 52 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,4 +96,55 @@ https://grafana.com/api/dashboards/13320/revisions/4/download
9696
https://grafana.com/api/dashboards/13325/revisions/4/download
9797
https://grafana.com/api/dashboards/13321/revisions/6/download
9898
```
99-
After that, your issue should be resolved and you should be able to see all the graphs on UI.
99+
After that, your issue should be resolved and you should be able to see all the graphs on UI.
100+
101+
#### 6. Unable to Login Devtron dashboard even if the password is correct
102+
103+
If you are not able to login into Devtron dashboard even after giving the correct password, it is possible that the argocd token of previous session has been stored in the cookies and is not able to override the new token that is generated for the new session. If you are facing this issue, follow the steps below -
104+
105+
If using Firefox -
106+
1. Goto login page of Devtron and open inspect.
107+
2. Navigate to storage tab in inspect.
108+
3. Click on url where Devtron has been installed under `Cookies` tab and you could see an argocd token with its value, something similar to below image.
109+
![inspect-cookies](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/devtron-troubleshooting/argocd-cookie.png)
110+
4. Now right click on token, and click on `Delete All Session Cookies` option.
111+
112+
If using Chrome -
113+
1. Goto login page of Devtron and open inspect.
114+
2. Navigate to Application tab, and under `Storage` tab click on `Cookies`.
115+
3. Click on url under `Cookie` and you would be able tto see an argocd token with its value, as shown in the image below.
116+
![chrome-cookie](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/devtron-troubleshooting/chrome-cookie.png)
117+
4. Now right click on token and click on `delete` option.
118+
119+
If using Safari -
120+
1. Goto Safari preferences >> Advanced options and check the show develop menu as shown in the image below.
121+
![safari-preferences](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/devtron-troubleshooting/safari-preferences.png)
122+
2. Now goto login page of Devtron and press `option+command+I`. It will open inspect element.
123+
3. Then navigate to `Storage`, click on `Cookies` and you would be able to see an argocd token with its value as shown in the image below.
124+
![safari-cookie](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/devtron-troubleshooting/safari-cookie.png)
125+
4. Now right click on token and select `delete` option.
126+
127+
After clearing `Cookies`, try again to login, you should be able to login now.
128+
129+
130+
#### 7. No charts found in Charts Discover Section
131+
132+
In the Devtron's Discover Chart section, if you are not able to see any charts available, goto `Global Configuration` >> `Chart Repositories` and click on `Refresh Chart` at the top-right as shown in the image below. After clicking the button, it might take 4-5mins to show all the charts in `Discover` section depending upon the chart repositories added.
133+
![charts-not-found](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/devtron-troubleshooting/refresh-charts.png)
134+
135+
136+
#### 8. Not able to update cluster
137+
138+
In `Global Configurations` >> `Cluters & Environments`, if you try to update a cluster which has been already added in Devtron, you might get an error as `{"message":"Failed to update datasource. Reload new version and try again"}`. If you are facing such issue, please follow the following steps -
139+
140+
1. Edit the changes you want to make in respective cluster
141+
2. Click on save after making changes and you may get error message stated above.
142+
3. Go to cluster where devtron has been installed and execute - `kubectl -ndevtroncd delete po -l app=devtron`
143+
4. Now refresh the page and you should be able to save it.
144+
145+
[Note: If you already have created some environments in that cluster, it needs to be updated again]
146+
147+
148+
149+
150+

0 commit comments

Comments
 (0)