Thanks to visit codestin.com
Credit goes to github.com

Skip to content

bug: unable to start a workspace when header command is needed #17687

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
MrPeacockNLB opened this issue May 6, 2025 · 3 comments
Closed
1 task done

bug: unable to start a workspace when header command is needed #17687

MrPeacockNLB opened this issue May 6, 2025 · 3 comments
Labels
needs-triage Issue that require triage

Comments

@MrPeacockNLB
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If I use --header command to get a needed header to get access to the coder instance then I am unable to start a stopped workspace.

Image

it seems the header was not set so it can not get access and dumps the nonsens warning message invalid charater.

Relevant Log Output



Expected Behavior


Coder CLI should also be aware of header command when starting a stooped workspace. So starting simply works


Steps to Reproduce


    

  1. Wait until a workspace is stopped in local VSCode
    2. 

  2. Reload Window while network was down (has nothing to do with the issue)
    3. 

  3. When VSCode asks to start the stopped workspace say yes
    4. 

  4. Boom
    5. 



Environment


    

  • Host OS: Manjaro Linux
    • 

  • Coder version: v2.20.2
    • 



Additional Context


No response

      		
    

      
  





        



            
            

              
            

        

      


      
    








      

    



      

  
            

    

      
    

    


      

          @MrPeacockNLB
MrPeacockNLB




          added
  the 

  needs-triage

  Issue that require triage
 label


      May 6, 2025

    

  








      

  
      



  

  @MrPeacockNLB





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  Author


  


  

    

  





      


        


  
    

      
          
I forget to mention that the coder instance is behind a Azure AppProxy. From there comes the invalid character when not passing the needed OAuth2 header in.

      		
    

  





        


            

            
            

              
            

        

      


      

            
  

    
  
    
    

  

  


    












      

  
      



  

  @MrPeacockNLB





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  Author


  


  

    

  





      


        


  
    

      
          
just calling coder start [ws] --header-command seems to work. Then the VSCode Coder Extension did not pass the --header-command as shown in the screenshot above.

      		
    

  





        


            

            
            

              
            

        

      


      

            
  

    
  
    
    

  

  


    












      

  
          

  

    
  


  

      

    @bjornrobertsson
bjornrobertsson



    mentioned this issue
    
      May 6, 2025
    





  


  

      
  
  Open

  







  









      

  
      



  

  @MrPeacockNLB





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  Author


  


  

    

  





      


        


  
    

      
          
closing this issue as it is tracked in vscode-coder repository

      		
    

  





        


            

            
            

              
            

        

      


      

            
  

    
  
    
    

  

  


    












      

  
            

    


    

    

      
    

    


      

          @matifali
matifali




            closed this as completed


      May 7, 2025

    

  


    











  
  

    

      

  





  




  
  

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



  






  
                  




    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

      

    needs-triage

  Issue that require triage








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
    

    Development
  




            
    
No branches or pull requests







      
    

  




      

    

  
      

  

    

      2 participants
    

    

        
          @matifali 
        
          @MrPeacockNLB