!Hubzilla Support ForumI've just cloned my account to a new hub as I've learnt I'm on an experimental node which could become unstable if the admin decides up update. When I try to connect to a new contact I'm told I don't have the premium channel app installed even though I have. Is this just a sync issue and something that will resolve itself eventually?

if i'm the "they" you tried to connect to i can disconnect and we can try again.

i think this happened because i had been connected to you earlier (one-way) and when you tried to connect that connection was activated w/o reporting anything. doesn't matter if you did this from your old or new hub since connections are synced.

but i don't have "premium channel" active or even installed.

edit: now i remember that the same thing happened when i wanted to connect to mike mcgarvin. whenever i clicked 'connect' i got a popup about premium channel. at that time i installed it, but the result remained the same, so i uninstalled it again, thinking mike is too busy and has some restriction on connections.

happy to, but first i need to know if it was really me joltrans was talking about. if yes, should both of us disconnect again or only he? that was the state before this happened. i was connected to him one-way and when he tried to start a connection he couldn't and apparently got this error. waiting for him to come back now...

i used to have my own pod (diasp.phanisvara.com) and federation worked fine. then i deleted that pod and this hub (hub.phanisvara.com) still tries to send to diasp.phani... but doesn't even attempt to deliver to diasp.org, the pod i'm using now.

yes, i got a one-way connection to you again, as before. now try to create a NEW connection. that's what happened the last time. i suspect, as you did, that it'll work. some sync-stuff got mixed up. let's see...

joltrast still hasn't confirmed that it happened again. if it does i think it's my hub's fault. i'll start this over again anyway, better than trying to debug why it doesn't federate properly. i have two clones, so there's no real loss.

joltrast still hasn't confirmed that it happened again. if it does i think it's my hub's fault. i'll start this over again anyway, better than trying to debug why it doesn't federate properly. i have two clones, so there's no real loss.

Joltrast said....

I just tried to connect to you now. Pressing connect from the profile pic does nothing. trying toconnect from your profile page reproduces the original error.

I deleted all conections several hours ago once I had reproduced the error. As I said, you can initiate a connection, I cannot. When I get the error, that's when you see a connection request on your hub.

no, i didn't see any connection request from you. but i'm going to scrap the thing anyway now. posts from me don't get sent to diaspora, but when i'm on my tiksi.net account they do. something went wrong and instead of trying to figure out what i'll just rebuild the whole thing. after that we can try again. i'll let you know via diaspora and i'd be surprised if the same error happened again. was probably my (hub's) fault all along.

in the meantime i rebuilt my hub, but at the same address, and again diaspora won't federate. @Mario Vavti pointed out that diaspora will reject messages from the same address because the crypto keys changed with the new installation. so i'll have to change the hub's address. now trying to find out if that can be done after the installation w/o too much trouble...

mario v. just said creating a new channel should be enough, no need to change the address. that way i'll lose all my contacts, but those can be recreated. and i should probably delete the current profile so no federation attempts continue to that one, right?