Fresh install, domain not working

Support
1

Hi all,

I’ve just completed a fresh install of Yunohost on Debian Jessie, everything seemed to complete without errors and I can access the server over local ip.

I registered a noho.st domain during install, but when I try to goto the domain I get a server not found error. I’ve installed Yunohost before and the domain has always worked fine. I waited over night to see if DNS would propogate but the page still does not load.

Thanks for any help
Jordy

Edit: I have ports 80 and 443 forwarded and I can connect to the server by its public ip

2

I have made a fresh install of jessie + yunohost using ‘nohost.me’ instead of ‘noho.st’ and I’m still seeing the same error. the domains are; plumbus.noho.st plumbus.nohost.me

edit: I get the following error when I run ‘yunohost dyndns update’

3

You might encounter an issue. This two domains are well registered but lead to nowhere.

4

Is there a way I can make it work? ive tried just about all i can think of

5

@JordyV could you try yunohost dyndns update -d plumbus.noho.st --verbose please ?
If your domain is really plumbus.noho.st, because I saw both noho.st and nohost.me on our dyndns server. Note that you can only have one dyndns per installation.

6

Yes, the domain is plumbus.noho.st, when it didn’t work originally i also tried nohost.me
The only domain attached to yunohost is the noho.st one.

Here are the results from that command

7

Wow, YunoHost do not handle IPv6?
Shit software :smile:
How do you want to do self-hosting with IPv4?

8

@Moul : thanks for your support, it really helps us moving forward.

@JordyV : is your server have an IPv4 connectivity, or IPv6 only ?

9

@JordyV also, can you tell us what’s in the /etc/yunohost/dyndns folder ?

I investigate this error, and it seems that there is no dnssec key on your server; You can force a key generation by doing :

cd /etc/yunohost/dyndns
dnssec-keygen -a hmac-md5 -b 128 -r /dev/urandom -n USER plumbus.noho.st
chmod 600 /etc/yunohost/dyndns/*.key /etc/yunohost/dyndns/*.private

and then paste us the output of yunohost dyndns update -d plumbus.noho.st --debug.

10

Here are the results of ‘ls -a’ in that directory, if I should check another way let me know

plumbus@plumbus:~$ cd /etc/yunohost/dyndns
plumbus@plumbus:/etc/yunohost/dyndns$ ls -a
.  ..  Kplumbus.nohost.me.+157+21297.key  Kplumbus.nohost.me.+157+21297.private  zone

I ran the code above as root and I got the following error

root@plumbus:/etc/yunohost/dyndns# yunohost dyndns update -d plumbus.noho.st --debug
55   DEBUG loading actions map namespace 'yunohost'
59   DEBUG extra parameter classes loaded: ['ask', 'password', 'required', 'pattern']
60   DEBUG initializing base actions map parser for cli
61   DEBUG registering new callback action 'yunohost.utils.packages.ynh_packages_version' to [
'-v', '--version']
5124 ERROR An instance is already running

Thanks again for your help

edit:
I reboot the server and rand the above dyndns command again, here is the result

root@plumbus:/etc/yunohost/dyndns# yunohost dyndns update -d plumbus.noho.st --debug
47   DEBUG loading actions map namespace 'yunohost'
52   DEBUG extra parameter classes loaded: ['ask', 'password', 'required', 'pattern']
52   DEBUG initializing base actions map parser for cli
53   DEBUG registering new callback action 'yunohost.utils.packages.ynh_packages_version' to [
'-v', '--version']
111  DEBUG lock has been acquired
1057 INFO processing action [1545.1]: yunohost.dyndns.update with args={'domain': 'plumbus.noh
o.st', 'key': None, 'dyn_host': 'dyndns.yunohost.org', 'ipv4': None, 'ipv6': None}
4836 INFO IPv6 connectivity is not available
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id:      0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;noho.st.                       IN      SOA

;; UPDATE SECTION:
plumbus.noho.st.        0       ANY     A       
plumbus.noho.st.        0       ANY     AAAA    
plumbus.noho.st.        0       ANY     MX      
plumbus.noho.st.        0       ANY     TXT     
pubsub.plumbus.noho.st. 0       ANY     A       
pubsub.plumbus.noho.st. 0       ANY     AAAA    
muc.plumbus.noho.st.    0       ANY     A       
muc.plumbus.noho.st.    0       ANY     AAAA    
vjud.plumbus.noho.st.   0       ANY     A       
vjud.plumbus.noho.st.   0       ANY     AAAA    
_xmpp-client._tcp.plumbus.noho.st. 0 ANY SRV    
_xmpp-server._tcp.plumbus.noho.st. 0 ANY SRV    
plumbus.noho.st.        1800    IN      A       121.220.1.97
plumbus.noho.st.        14400   IN      MX      5 plumbus.noho.st.
plumbus.noho.st.        14400   IN      TXT     "v=spf1 a mx -all"
pubsub.plumbus.noho.st. 1800    IN      A       121.220.1.97
muc.plumbus.noho.st.    1800    IN      A       121.220.1.97
vjud.plumbus.noho.st.   1800    IN      A       121.220.1.97
_xmpp-client._tcp.plumbus.noho.st. 14400 IN SRV 0 5 5222 plumbus.noho.st.
_xmpp-server._tcp.plumbus.noho.st. 14400 IN SRV 0 5 5269 plumbus.noho.st.

; TSIG error with server: tsig indicates error
update failed: NOTAUTH(BADSIG)
5205 DEBUG action [1545.1] ended after 4.147s
5205 DEBUG lock has been released
5205 ERROR Unable to update IP address on DynDNS
11

Hi there,

I’ve been having trouble with my Yunohost installation. Everything is fine except that the domain (ending in noho.st) does not always lead to my server. The ports check site shows me that the ports are closed for the domain, even though they are open in my router. That happens on an off and on basis with no real indication of what the error is.

Could it be an issue that I have the same domain name open with a nohost.me ending from a very old install I don’t use anymore? Could that be an interfering problem?

12

The nohost.me Domain is now deleted and my server has a lot more uptime, but it is still not reachable 24/7. Is there a way to find out what the problem is? Maybe you could tell me if there is a log of some sort that keeps track of the DNS availability or something.