From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1689262937; bh=D+eOducSqicoatsWnpryuRcGZOWjwtkQOhA7qEx4u+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=j3a3Iekrg3alr0tifjfDEo0DntJfvITmC8BDBX56XvZqIfAC7374A0/uIe+z4Z9oN huW8cXjDXH9qTIjGV2HiOi92/QedxmrK8Z1B2918gzTGIudZlb5hDIhvOKODRYbCR2 LhEQscnpbRtJ02KwvZpVLaLT5W1lff9NTRsRchisFAeG3L0RijoWM1RNGmE3RQpnAK ccrx7T2yXAWbxXdfqfmQPE+XwOS+AbI4n1QogjeSCf87Rmwy7zHI1y7sLuthsB45pT YKA3d6gF7Yz9ziEZDWMR55Tg615t3F06lYaS3kQqh+P6nvgMAl3/VZgdMTJ14V/JAx Jvu+GBoKi4Wmg== Received: from biznet-home.integral.gnuweeb.org (unknown [182.253.126.105]) by gnuweeb.org (Postfix) with ESMTPSA id 6AA3024A9B0; Thu, 13 Jul 2023 22:42:15 +0700 (WIB) Date: Thu, 13 Jul 2023 22:42:06 +0700 From: Ammar Faizi To: Alviro Iskandar Setiawan Cc: Michael William Jonathan , GNU/Weeb Mailing List Subject: Re: [PATCH server-haj002 v1 0/6] Server update and new service elk.gnuweeb.org Message-ID: References: <20230713152850.5565-1-alviro.iskandar@gnuweeb.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230713152850.5565-1-alviro.iskandar@gnuweeb.org> X-Bpl: hUx9VaHkTWcLO7S8CQCslj6OzqBx2hfLChRz45nPESx5VSB/xuJQVOKOB1zSXE3yc9ntP27bV1M1 List-Id: On Thu, Jul 13, 2023 at 05:28:44PM +0200, Alviro Iskandar Setiawan wrote: > The elk service for GNU/Weeb is now up and ready to use at: > > https://elk.gnuweeb.org I can login using my GNUWeeb-Mastodon account on that web. But I see many network errors in the browser console: """ Access to fetch at 'https://social.gnuweeb.org/nodeinfo/2.0' from origin 'https://elk.gnuweeb.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. """ It seems you need to add 'Access-Control-Allow-Origin' header in the nginx host config to fix it. -- Ammar Faizi