#108 Slow repo browsing

Fechado
aberto por dmz 10 meses atrás · 6 comentários
dmz comentou 10 meses atrás

A couple of weeks ago, Teknik was offline for several hours, not sure what happened but, since then, accessing git repos, browsing folders and committing changes became slower than usual. Maybe some caching issue.

A couple of weeks ago, Teknik was offline for several hours, not sure what happened but, since then, accessing git repos, browsing folders and committing changes became slower than usual. Maybe some caching issue.
Uncled1023 adicionou a etiqueta
Bug
10 meses atrás
Uncled1023 comentou 10 meses atrás
Proprietário

I’ll have to look into this.

I'll have to look into this.
dmz comentou 8 meses atrás
Autor

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 comentou 8 meses atrás
Proprietário

@dmz Yea, it was just a network issue with the server.

@dmz Yea, it was just a network issue with the server.
dmz comentou 8 meses atrás
Autor

Just a follow-up, committing changes can take up to ~2 min and since the last downtime, it’s always returning the error message below. Nonetheless, hitting the browser back button returns to the editing page and by cancelling, I realize the changes have been successfully committed.

502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.

Just a follow-up, committing changes can take up to ~2 min and since the last downtime, it's always returning the error message below. Nonetheless, hitting the browser back button returns to the editing page and by cancelling, I realize the changes have been successfully committed. > 502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
Uncled1023 comentou 7 meses atrás
Proprietário

@dmz This should now be fixed. Can you give it a whirl and see if you notice the slowdowns anymore?

@dmz This should now be fixed. Can you give it a whirl and see if you notice the slowdowns anymore?
dmz comentou 7 meses atrás
Autor

Thanks a lot @Uncled1023.
I tested it and it seems back to normal speed.
Cheers.

Thanks a lot @Uncled1023. I tested it and it seems back to normal speed. Cheers.
Acesse para participar desta conversação.
Sem marco
Sem responsável
2 participante(s)
Data limite

Data limite não informada.

Dependências

Esta issue atualmente não tem dependências.

Carregando…
Cancelar
Salvar
Ainda não há conteúdo.