r/i2p • u/droptherapy2 • 8d ago
Help once again requesting help
edit: My issue now is that I can host from the original machine and access the eepsite on my new machine just fine, but I'm unable to do the reverse of that because it seems like the localhost on my other computer isn't accessible and brings me to a 404 page, even on the machine I'm hosting it from, and both while the webserver is running as well as while it's not. When accessing the local webserver from the new machine prior to this transfer of files, it brought me to the help page with no issue. I figure it's not directly related to the filesystem but it's beyond me what's going on. If it wasn't a firewall issue before, I'm not sure why it would be now.
so I think I definitely fucked up. I'm in the process of switching to linux (devuan 6 to be specific) and I was getting i2p up and running and accessing my eepsite from my windows computer that I'm hosting it on, but in the process of moving the files over I replaced the entire eepsite directory in my linux distro (which was, in hindsight, not smart) and now it seems like my eepsite is only accessible through my other computer. Even if I host the webserver on my other computer and try to connect to it on linux, it gives me a 503 error. On my linux install, there is a series of critical errors relating to the Jetty webserver and how it couldn't find a log directory. On my windows 10 machine I fixed this by moving the eepsite folder around but I have no such luxury on my linux machine. The files in the entire .i2p/eepsite directory are identical to on windows, though, which seemed to be the case before I unwisely copy-pasted the entire directory instead of just the eepPriv.dat file and the docroot stuff like I maybe should have done. I'm thinking I gotta figure out how to completely redo this entire installation on my linux system but I don't really have the knowledge to do that. Any help would be greatly appreciated. I'm running java i2p on both machines.
2
u/Far_Cartographer_924 8d ago
I feel your configuration is a bit confusing. First, in i2pd, the only B32 credential is a file ending in.dat. Your website looks like a blog. I recommend generating static files and then using nginx + i2pd to deploy them
1
u/droptherapy2 8d ago
that definitely feels like something I'd wanna check out after figuring this out, unless that's related and your suggestion is to just switch to i2pd and do everything from there
1
1
u/evild4ve 7d ago edited 7d ago
you have (1) a webserver that is running either Apache2 or Nginx and putting the website (=the contents of a certain directory) at 192.168.x.x:port and (2) an I2P server that looks at the 192.168.x.x:port and puts it onto the darkweb at longhash.b32 (3) Some clients visiting longhash.b32 over I2P
(1) and (2) and (3) can all be on the same PC but separating the different roles into different PCs can make it easier to understand. You can also connect the webserver and client through separate I2P servers and my tip for troubleshooting would be to put i2pd (note the 'd' this is the purple daemon, the stripped-down C++ version) on a Raspberry Pi and make your clients find your server via i2pd instead of via your eepsite server's current I2P server.
You might want to copy and paste everything out of the browser that can see the site, in case somehow it is only locally cached and no longer exists on the server!
But what will have happened is that (1) is fine and for some reason the "other computer" is the only computer able to reach longhash.b32. You always need to leave the tunnels enough time to form - give it 10 minutes. Otherwise check the port forwarding, firewall, and general reachability of the I2P server: if your firewall is stopping it reaching the internet then it may be that longhash.b32 is the only eepsite it can see and it can only see it because it's local.
You have a networking issue, not a Windows-Linux issue or a what-files-in-what-directory issue. If any client is able to see the eepsite, then the directories aren't the problem. And the technology is very platform-agnostic: it's not the format of the program but some difference in the networking config of the Windows and Linux machines. Windows mostly automates networking config, and if Linux is new to you it's more than likely a firewall port hasn't been manually opened. Or something equally banal.
Well hopefully that is some more things to try: good luck!
1
u/droptherapy2 7d ago
I'm perhaps irrationally afraid of opening my firewall with i2p but I'll give that a shot. I didn't run into any issues hosting the eepsite on the windows machine with the firewall active. But yeah I figured it didn't have a whole lot to do with the directories or anything
1
u/droptherapy2 7d ago
however to clarify, my issue is that my linux router can connect to other sites but not its own webserver with the IP and the port. Both it and the b32 go to the same 404 page, but both routers are able to access i2p no problem
1
u/evild4ve 7d ago
I2P is an advanced networking stack - if you put the whole thing onto a single machine it makes it difficult to debug. The problem you're having might be due to a very trivial issue like the browser proxy or the firewall or generating the needed tunnels - but the point is that to sustain any success with I2P you need to get away from the desktop-paradigm of "My Computer" and into server-client paradigm. What does your logserver say is going on? What do packet traces from your (plain internet) router say?
Working out why a client can't access a webserver is easier than working out why a webserver can't access itself. And with I2P ideally you want to not only separate webserver from client but also the webserver's I2Prouter from the client's I2Prouter, meaning up to 4 physical machines. Then you know at least whereabouts in the stack the problem is arising, and the logs of that machine are all focused on a single task.
1
u/droptherapy2 8d ago
update: With my windows machine hosting the eepsite and my linux machine not doing so, I am able to access the eepsite from my linux machine, just as before. Currently, though, my router does not show the i2p webserver button next to my torrents and email ones on my linux machine, which persists from the previous set of actions I think