Phillip Jensen
Phillip Jensen
This has been one of my wishes for a long time, but the main blocker for now is that inbound/outbound networking is not supported yet. Outbound networking should come later...
Experiencing same issue on Ubuntu 18.04 with Golem version 0.22.1
Being stuck at the connecting screen can sometime be caused by not having your ports forwarded. (40102, 40103 and 3282)
[yagna_r2022-10-07_12-42-53.log](https://github.com/golemfactory/yagna/files/9734705/yagna_r2022-10-07_12-42-53.log) [ya-provider_r2022-10-07_12-42-57.log](https://github.com/golemfactory/yagna/files/9734706/ya-provider_r2022-10-07_12-42-57.log)
+1 - would be useful for the stats page too. Right now on stats I have this script that Docker is running on the container ```bash #!/bin/sh set -e #...
Issues with the stats page right now... checked the instance, healthcheck is not returning any errors as its able to fetch from the Yagna REST API ``` ubuntu@stats:~$ docker exec...
Now I re-ran the `yagna payment status` command twice and suddenly it returns fine, but yagna still doesn't work correctly and doesnt retrieve offers. ``` /stats-backend # yagna payment status...
Following this as I have the issue here https://github.com/timescale/helm-charts/issues/492
Bump. Following this
We have providers reporting on 0.12.0 that this is happening again "The yagna process is still increasing. 1.3GB more than about a day ago. It seems most increases occur when...