#108 Slow repo browsing

Cerrada
abierta hace 11 meses por dmz · 6 comentarios
dmz comentado hace 11 meses

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 added the
Bug
label hace 11 meses
Uncled1023 comentado hace 11 meses
Propietario

I’ll have to look into this.

I'll have to look into this.
dmz comentado hace 8 meses
Autor

Another 9h downtime yesterday. Are the servers OK?

Another 9h downtime yesterday. Are the servers OK?
Uncled1023 comentado hace 8 meses
Propietario

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

@dmz Yea, it was just a network issue with the server.
dmz comentado hace 8 meses
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 comentado hace 8 meses
Propietario

@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 comentado hace 8 meses
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.
Inicie sesión para unirse a esta conversación.
Sin Milestone
No Assignees
2 participantes
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Cargando…
Cancelar
Guardar
Aún no existe contenido.