Issue Running Hidden Service on Fedora #13343

issue Rspigler openend this issue on May 29, 2018
  1. Rspigler commented at 7:49 pm on May 29, 2018: contributor

    Describe the issue: Some recent update to my Fedora system killed the connections I had to my hidden service. I’ve attempted re-installing, restarting tor (systemctl restart tor.service), and restarting Bitcoin Core, but to no avail.

    I have the following in my torrc file:

    HiddenServiceDir /var/lib/tor/bitcoin-service/ HiddenServicePort 8333 127.0.0.1:8333

    And the following in bitcoin.conf:

    onion=127.0.0.1:9050 listen=1 externalip=ONION_ADDR discover=1

    ONION_ADDR was found by cat /var/lib/tor/bitcoin-service/hostname

    What behavior did you expect?: Not losing my connections, or regaining connections upon reinstall.

    How reliably can you reproduce the issue, what are the steps to do so?: Just install Fedora 28, Bitcoin Core, and attempt to set up a Tor node.

    What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?: Bitcoin 0.16.0 from BitcoinCore.org (verified!).

  2. fanquake added the label Linux/Unix on May 29, 2018
  3. fanquake added the label P2P on May 29, 2018
  4. marcoagner commented at 3:19 pm on June 1, 2018: contributor
    It may be an issue with your Fedora/SELinux policy. Have you tried investigating these?
  5. Rspigler commented at 6:18 pm on June 19, 2018: contributor

    Sorry, been out of the country for the last two weeks.

    It is not a SELinux policy issue - running setenforce 0 and restarting Bitcoin Core still doesn’t allow any connections to my hidden service.

    I should note that updating to 0.16.1 has not changed this (not that there was any indication there was supposed to be a fix for this included in the update).

  6. Rspigler commented at 11:16 pm on June 25, 2018: contributor

    So, had been testing my connections using https://bitnodes.earn.com

    This is still failing for some reason, but I have gained 2 connections back to my Tor node today. This is after I attempted restarting firewalld (in addition to restarting Bitcoin Core, SELinux, and tor like mentioned above in my initial post). Not sure if that’s what fixed this, or the recent kernel update from 4.16.16 to 4.17.2 that Fedora pushed? But anyway, closing this now.

  7. Rspigler closed this on Jun 25, 2018

  8. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-01-15 09:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me