Hardware: Raspberry Pi4 at home YunoHost version: 4.1.7.2 I have access to my server : through the web admin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Hello, new yunohost frens! I am trying to get my yunohost configured properly for the first time on my Raspberry Pi4 here at home. I am on the diagnosis screen in the web admin interface. I am currently unable to connect through HTTP from outside my local network, and all of my ports show up as unreachable. I am on Google Fiber and can reach my network admin settings to create forwarding rules, but they donât seem to take effect. I also have UPnP enabled on my network, and I ran command
$ sudo yunohost firewall reload as suggested here: https://yunohost.org/en/isp_box_config
I have poured over documentation for yunohost as well as Google Fiber and Iâm totally stumped. I would greatly appreciate some pointers if possible!
I tried manually entering the forwarding rules before, but it didnât work, so I tried executing the UPnP command on the Pi4 itself, that didnât seem to work either even though it displayed a âsuccessâ message
Also, in the Google documentation you referred to it mentions âchoose the tab for the the type of IP address youâre forwarding, IPv4 or IPv6â but I donât have an option to toggle tabs between IPv4/6 on my end.
Been looking further and found that the documentation you referenced uses the âGoogle Home appâ which I do not use, I have a Google fiber connection but the interface is slightly different than that of Google Home app.
I have attached a screen cap of the forwarding rules I tried manually, perhaps you might be able to tell what Iâm doing wrong?
I may just try to reflash the SD and start from square one, because initially I tried to use my own DNS and couldnât figure out that either, so then went over to the auto dns.
Iâve been working on trying to solve this issue. I have the ports open, and they show up as open from a port scanner but the diagnostic tools still show them as closed.
I ran the package upgrader, so now Iâm running YunoHost 4.2.6.1 and everything shows as up-to-date. I tried to use the YunoPaste feature to share my logs, but I get a 400 error when attempting.
I am running a Raspiblitz lightning node from the same area network; is this whatâs giving me my porting woes? Would love some help. I am ultimately trying to run Castopod from this yunohost server. I installed Castopod but when I try to import my podcast feed, I get an unspecific error that says âtry again laterâ
can you tell a bit more about what is this âport scannerâ that says ports are opened ? (Maybe they are, it gets a bit technical and depends on how / what test exactly is done to check if a port is opened)
Assuming your ports really are opened, are you able to access your server from the outside network (for example through a 3G/4G internet connection or whatever)
Apart from this, the last screenshot your provided sounds super legit to me ⌠I would just of course double-check that the âreversed IPâ is indeed the local IP of your server âŚ
Another way could be to enable the DMZ instead of port forwarding, but if port forwarding doesnât work, then it sounds more like something else somewhere is interfering âŚ
the port scanner is called âPortScan & Stuffâ was recommended to me by a friend. Softpedia entry about it here:
I can successfully reach my server off local network (I get an ssl warning but just click proceed) by visiting bowlafterbowl.nohost.me on my phone with wifi off, and can successfully log in. Some others helping me troubleshoot have also been able to get my server to pull up on their networks, although they of course canât get past the login screen without credentials.
The reserve IP is indeed correct for my Yunohost server. One question I am still unsure of: Is this port error possibly caused due to running a RaspiBlitz lightning node on the same local network? it is on a separate Pi with its own separate dedicated IP.
I am trying to remain positive as Iâd really love to get this solution up and running, my current podcasting host expires at the end of this month, but iâm getting nothing in terms of help or suggestions
Have you created all the recommended DNS records for your domain? It might not be a ports issue but maybe that youâre missing some of the DNS records? Yunohost needs a shit ton of DNS records for each domain. I had to add like 17 different DNS records for mine. You need to add all of these (with your actual info not the info in example) in order to get the ssl certificate to work
Basic ipv4/ipv6 records
@ 3600 IN A 111.222.33.44
3600 IN A 111.222.33.44
(If your server is IPv6 capable, there are some AAAA records)
@ 3600 IN AAAA 2222:444:8888:3333:bbbb:5555:3333:1111
3600 IN AAAA 2222:444:8888:3333:bbbb:5555:3333:1111
XMPP
_xmpp-client._tcp 3600 IN SRV 0 5 5222 your.domain.tld.
_xmpp-server._tcp 3600 IN SRV 0 5 5269 your.domain.tld.
muc 3600 IN CNAME @
pubsub 3600 IN CNAME @
vjud 3600 IN CNAME @
xmpp-upload 3600 IN CNAME @
Mail (MX, SPF, DKIM and DMARC)
@ 3600 IN MX 10 your.domain.tld.
@ 3600 IN TXT âv=spf1 a mx -allâ
mail._domainkey 3600 IN TXT âv=DKIM1; k=rsa; p=someHuuuuuuugeKeyâ
_dmarc 3600 IN TXT âv=DMARC1; p=noneâ
I still think that somehow this is a problem specific to IPv6âŚbut I have no clue how to troubleshoot IPv6; network configuration isnât something I have a lot of experience in.
Then itâs probably not a huge deal : network is a complicated matter and itâs a bit difficult to diagnose and debug stuff just from a forum
But basically if things do work in IPv4, then letâs just disable IPv6 entirely on your server (having IPv6 running is better for the general health of the internet, but life is too short to debug every computer problem)
Iâm on the train right now so Iâm struggling to google âdisable ipv6 on debianâ on Google, but basically this corresponds to two commands like âsysctl somethingâ your gotta type on your server
