Re: It just doesn't work

Jacob Hrbek <[email protected]> Thu, 15 Sep 2022 05:38:57 +0000
Newsgroups	gmane.network.gnunet.general
Message-ID	<[email protected]>
Relevant: 
<https://lists.gnu.org/archive/html/help-gnunet/2022-09/msg00001.html>

I didn't receive the messages from liquorice and t3sserakt, mail sent 
without being aware of these

On St, zář 14 2022 at 16:35:50 +0200, Jacob Hrbek 
<[email protected]> wrote:
> ### Steps to reproduce:
> 0. Get GNU Guix
> 1. Install gnunet using `$ guix install gnunet`
> 2. Read documentation and figure out that you need to do this 
> configuration
> 
>     $ cat ~/.config/gnunet.conf
>     [dns2gns]
>     OPTIONS = -d 1.1.1.1 -p 5252
> 
>     [arm]
>     START_SYSTEM_SERVICES = NO
>     START_USER_SERVICES = YES
> 
>     #[gns]
>     #PORT = 2102
> 
>     #[gns-proxy]
> 
>     #[PATHS]
> 
> 3. Start gnunet using `$ gnunet-arm -c ~/.config/gnunet.conf -s`
> 
> 4. Try to do `$ chromium --proxy-server=socks5://127.0.0.1:7777 
> test.gnu` without success that gets you:
>     gnunet-gns-proxy-1365 ERROR Download curl test.gnu/ failed: 
> Couldn't resolve host name Refused wrong status code (0). HTTP 
> requires three digits status code! Application reported internal 
> error, closing connection
> 
> 5. Sink 18 hours in it reading the source code, reading the 
> configuration that is shipped with gnunet to try to adjust yours, try 
> to debug invidual services without success, ask other people who 
> demoralize you by telling you that they also weren't able to make 
> gnunet to lose all hope and write on the mailing list hoping for 
> miracle.
> 
> ### Expected behavior:
> 
> Run GNUNet in chromium to resolve http://test.gnu <http://test.gnu/> 
> and other gnunet websites while being able to use dns2gns for 
> clearweb through SOCKS5 proxy to be able to define a reproducible 
> configuration for deployment on guix.
> 
> ### Actual behavior:
> 
> Torture of the user
> 
> ### Additional Informations:
> a. All services that it gives me are running and doesn't seem to 
> report any issues (gns-proxy, dns2gns and messenger had to be 
> manually started using $ gnuner-arm -i SERVICE)
> 
>     $ gnunet-arm -I -a
>     All services:
>     (started: 9)
>     gns-proxy (binary='gnunet-gns-proxy', status=started)
>     dns2gns (binary='gnunet-dns2gns', status=started)
>     identity (binary='gnunet-service-identity', status=started)
>     messenger (binary='gnunet-service-messenger', status=started)
>     namestore (binary='gnunet-service-namestore', status=started)
>     reclaim (binary='gnunet-service-reclaim', status=started)
>     rest (binary='gnunet-rest-server', status=started)
>     zonemaster (binary='gnunet-service-zonemaster', status=started)
>     zonemaster-monitor (binary='gnunet-service-zonemaster-monitor', 
> status=started)
> 
> b. I don't have public IP configured
publickey - [email protected] - 1677db82.asc (application/pgp-keys, 713 B)
signature.asc (application/pgp-signature, 249 B)