504 are typically connections to the database that fail due to not being able to connect to php-fpm. It can also be when php-fpm cannot connect to the dbServer. Typically due to network latency. This can happen even when connected to localhost when the network gets busy. As it is still effected by the TCP/IP stack.
If your server stack is completely on one physical computer try using sockets instead of TCP/IP to connect your httpd with php-fpm. You need to configure that on both sides, your httpd and php-fpm.
I don't have a server, only a client (Firefox browser). 504 is Gateway Time-Out error. So it is just the slow response of friendica that causes problems at times. It does not bother me, at my age I'm a wee bit slow as well 😀
My bad, I thought you were saying that you were having this issue with your instance of Friendica. I did not realize you were just talking about connecting to the friendica.world server.
Yes, @Ruud server's 504's are likely due to the overload of so many new users and other problems he has mentioned.
I am. I am also setting up an instance friendica.rogueproject.org. I was waiting until I have more experience dealing with friendica before I offered. At this point I have.
I am still having issues though I expect to be fully up and running in about a week. Right now the (PHP) routing is not correct. Not sure why and have not had time to correct the issues.
But yes I would love to get a chance to help you and learn more. I just found out that friendica existed a week or so ago and I just stared setting up an instance yesterday. So this is a learning process for me. Though whatever I can do to help, let me know. I am always interested in learning more.
I have setup the instance using docker. I'm very interested in the differences in running it without docker, as I think some issues we have might be related to the docker install.
I am going to also setup a test instance, we might do that together? I'm about to leave to Brussels to attend #fosdem so that install will be after the weekend.