Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

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

Live Logging of Jobs does not work behind Apache Reverse Proxy #1808

Closed
Renasb23 opened this issue Mar 6, 2024 · 1 comment
Closed

Live Logging of Jobs does not work behind Apache Reverse Proxy #1808

Renasb23 opened this issue Mar 6, 2024 · 1 comment

Comments

@Renasb23
Copy link

Renasb23 commented Mar 6, 2024

Hello,

I have installed and used Ansible Semaphore for a while but have currently changed to it running behind an Apache reverse Proxy for SSL connections.
The entire UI works fine except for the live Logging when you run a job.

Instead of showing the running log and status of the Job it just stays at "waiting" until I reload the Page. Afterwards, I can see the log.

Did I forget to add something?

The Apache Log also throws this error:
[proxy_http:error] [pid 3335698] (20014)Internal error (specific information not available): [client ...:51279] AH01102: error reading status line from remote server localhost:3000
[Wed Mar 06 11:01:37.966326 2024] [proxy:error] [pid 3335698] [client ...:51279] AH00898: Error reading from remote server returned by /api/ws

I entered the full Link with which Semaphore is called in the web_host
Apache Config relevant lines:
(Default.conf)
Redirect permanent /api/ws ws://semaphorehost.de:3000/api/ws
Redirect permanent /semaphore https://semaphorehost.de

(Default-ssl.conf)
SSLEngine on
SSLProxyEngine on
ProxyPass / http://localhost:3000/
ProxyPassReverse / http://localhost:3000/

@fiftin
Copy link
Collaborator

fiftin commented Mar 6, 2024

I think problem with Websocket config in Apache

@semaphoreui semaphoreui locked and limited conversation to collaborators Mar 6, 2024
@fiftin fiftin converted this issue into discussion #1811 Mar 6, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants