Project

General

Profile

Actions
Copy link

Bug #17883

closed

Can't access on technique editor

Added by Anonymous almost 4 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Web - Technique editor
Target version:
6.1.1
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
70
Name check:
To do
Fix check:
Checked
Regression:

Description

!! Hello :)

I update recently my rudder server, and since I can no longer access on Technique Editor (/rudder/secure/configurationManager/techniqueEditor).
I have a 404. (I can't send screenshot, in this issue, I have a 403 http code with https://issues.rudder.io/uploads.js?attachment_id=3&filename=rudder.png&content_type=image%2Fpng)

But HTTP request send a 200 status code and there are no log with when I access on this page (test with a tail -f /var/log/rudder/*/*.log )

PostgreSQL is running, all other module work and disk free is ok.

Thank :)

Actions
Copy link
 #1

Updated by Anonymous almost 4 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by François ARMAND almost 4 years ago

So, the problem is likely that an apache configuration file was not updated correctly.
The faulty file is:

/opt/rudder/etc/rudder-apache-webapp-ssl.conf

It should contain the line:

ProxyPass /rudder/relay-api !

(and not <Location /rudder/relay-api> etc).

Perhaps do you have the new, correct file in: /opt/rudder/etc/rudder-apache-webapp-ssl.conf.dpkg-dist. If so, you need to move that file to /opt/rudder/etc/rudder-apache-webapp-ssl.conf

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 4 years ago

To add some precision, the proxypass may be an issue too, but the problem (accessing technique editor) is because of the missing directives about in the old apache conf

# Technique editor (aka 'ncf builder')
Alias /ncf-builder /usr/share/ncf/builder
<Directory /usr/share/ncf/builder>
  # Allow access from anybody
  Require all granted
</Directory>

The proxy change, which is a change between 5.0 and 6.0 cause the apache config to not be updated in 6.1 (but it should have been updated but that another issue)

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 4 years ago

  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2322
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from In progress to Pending release
Actions
Copy link
 #7

Updated by Anonymous almost 4 years ago

I add the config in https://issues.rudder.io/issues/17883#note-3
It work
Thank :)

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.2 to 6.1.1
Actions
Copy link
 #9

Updated by François ARMAND almost 4 years ago

  • Category set to Web - Technique editor
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 70
Actions
Copy link
 #10

Updated by François ARMAND almost 4 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.1 which was released today.

Actions
Copy link

Also available in: Atom PDF