charm icon indicating copy to clipboard operation
charm copied to clipboard

RPM on Fedora 35 and Odd Port Used

Open ProfessorManhattan opened this issue 2 years ago • 0 comments

Just wanted to let you know that after installing the RPM on Fedora 35, when I enter charm link I'm greeted with something that looks like it exits early. It shows the linking progress indicator in a frozen state and just skips to showing my prompt again.

~ on ☁️  [email protected] 
❯ charm link
                                                            
  You can link the SSH keys on another machine to your Charm
  account so both machines have access to your stuff. Keys  
  can be unlinked at any time.                              
                                                            
  ⣽  Generating link...                                     

~ on ☁️  [email protected] 
❯ charm fs

~ on ☁️  [email protected] 
❯ charm link
                                                            
  You can link the SSH keys on another machine to your Charm
  account so both machines have access to your stuff. Keys  
  can be unlinked at any time.                              
                                                            
  ⣽  Generating link...                                     

~ on ☁️  [email protected] 
❯ charm link

Also, when I run charm after installing the regular old Linux binary, I get the following error which is because my firewall has restrictions on outgoing ports:

❯ charm
                                                                                
   Charm                                                                        
                                                                                
  Uh oh, there’s been an error: dial tcp 18.214.45.34:35353: connect: connection
                                                                                

~/Downloads/charm_0.9.2_linux_x86_64 on ☁️  [email protected] took 3s

It might make sense to use NGINX to proxy 443 (or 80) to 35353 for your production server since this might be a common issue with people behind restrictive enterprise firewalls

ProfessorManhattan avatar Jan 18 '22 00:01 ProfessorManhattan