MuWire is connecting, please wait.

[ghost]

I've read on a similar issue that I have to copy and paste the logs, but I'm on Manjaro and I don't know where they are.

[zlatinb]

Are you using the AppImage or the package from AUR? If you are using the AppImage are you using an embedded router or external router? (MuWire asks you that in the setup wizard or you can look in Options->I2P)

If you are using an embedded router it should connect after a few minutes at most. If you are using an external router or the package from AUR you need to make sure there is an I2P or I2Pd router running. The I2Pd router must have its I2CP interface enabled.

[ghost]

I'm using the AUR package. I've installed i2pd, and then I think I've enabled the router with sudo systemctl enable --now i2pd.service as it says in the wiki. I can see the i2pd webconsole at http://127.0.0.1:7070/ and this is what it displays:

<div class="header"><b>i2pd</b> webconsole</div>
<div class="wrapper">
<div class="menu">
  <a href="http://127.0.0.1:7070/">Main page</a><br><br>
  <a href="http://127.0.0.1:7070/?page=commands">Router commands</a><br>
  <a href="http://127.0.0.1:7070/?page=local_destinations">Local Destinations</a><br>
  <a href="http://127.0.0.1:7070/?page=tunnels">Tunnels</a><br>
  <a href="http://127.0.0.1:7070/?page=transit_tunnels">Transit Tunnels</a><br>
  <a href="http://127.0.0.1:7070/?page=transports">Transports</a><br>
  <a href="http://127.0.0.1:7070/?page=i2p_tunnels">I2P tunnels</a><br>
  <a href="http://127.0.0.1:7070/?page=sam_sessions">SAM sessions</a><br>
</div>
<div class="content"><b>Uptime:</b> 2 minutes, 50 seconds<br>
<b>Network status:</b> Firewalled<br>
<b>Tunnel creation success rate:</b> 31%<br>
<b>Received:</b> 361.33 KiB (2.32 KiB/s)<br>
<b>Sent:</b> 278.59 KiB (1.66 KiB/s)<br>
<b>Transit:</b> 0.00 KiB (0.00 KiB/s)<br>
<b>Data path:</b> /var/lib/i2pd<br>
<div class="slide"><label for="slide-info">Hidden content. Press on text to see.</label>

</div>
<b>Routers:</b> 141 <b>Floodfills:</b> 109 <b>LeaseSets:</b> 0<br>
<b>Client Tunnels:</b> 37 <b>Transit Tunnels:</b> 0<br>
<br>

HTTP Proxy | Enabled
-- | --
SOCKS Proxy | Enabled
BOB | Disabled
SAM | Enabled
I2CP | Disabled
I2PControl | Disabled

</div>
</div>

i2pd webconsole
[Main page](http://127.0.0.1:7070/)

[Router commands](http://127.0.0.1:7070/?page=commands)
[Local Destinations](http://127.0.0.1:7070/?page=local_destinations)
[Tunnels](http://127.0.0.1:7070/?page=tunnels)
[Transit Tunnels](http://127.0.0.1:7070/?page=transit_tunnels)
[Transports](http://127.0.0.1:7070/?page=transports)
[I2P tunnels](http://127.0.0.1:7070/?page=i2p_tunnels)
[SAM sessions](http://127.0.0.1:7070/?page=sam_sessions)
Uptime: 2 minutes, 50 seconds
Network status: Firewalled
Tunnel creation success rate: 31%
Received: 361.33 KiB (2.32 KiB/s)
Sent: 278.59 KiB (1.66 KiB/s)
Transit: 0.00 KiB (0.00 KiB/s)
Data path: /var/lib/i2pd
Hidden content. Press on text to see.
Routers: 141 Floodfills: 109 LeaseSets: 0
Client Tunnels: 37 Transit Tunnels: 0

Services HTTP Proxy Enabled
SOCKS Proxy Enabled
BOB Disabled
SAM Enabled
I2CP    Disabled
I2PControl  Disabled

But MuWire hasn't connected yet. Am I missing any steps?

[zlatinb]

Yes, the following needs to say "enabled":

I2CP | Disabled

To do that, add the following lines to $HOME/.i2pd/i2pd.conf

[i2cp]
enabled=true
address=127.0.0.1
port=7654

Then re-load the i2pd daemon and after it comes up saying that I2CP is Enabled restart MuWire.

[ghost]

I had to place the file in /var/lib/i2pd for it to show as enabled.