Skip to content
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

invalid URL scheme when using proxy #9194

Closed
corny opened this issue Sep 12, 2018 · 5 comments
Closed

invalid URL scheme when using proxy #9194

corny opened this issue Sep 12, 2018 · 5 comments

Comments

@corny
Copy link
Contributor

corny commented Sep 12, 2018

I am running a reverse proxy that does TLS and forwards requests via HTTP to the librenms host. Since last night I am not able to sign in any more, because the login contains two resources referenced via http:// instead of https://.

My config.php contains:

$config['base_url'] = "https://librenms.example.com";

Excerpt of the login page:

    <div class="panel-heading">
        <h3 class="panel-title center-block">
            <img class="logon-logo img-responsive" src="http://librenms.example.com/images/librenms_logo_light.svg">
        </h3>
    </div>
    <div class="panel-body">
        <div class="container-fluid">
            <form class="form-horizontal" role="form" action="http://librenms.example.com/login" method="post" name="logonform">
@corny corny changed the title https instead of https invalid URL scheme: http instead of https Sep 12, 2018
@corny corny changed the title invalid URL scheme: http instead of https invalid URL scheme when using proxy Sep 12, 2018
@MrXermon
Copy link
Contributor

MrXermon commented Sep 12, 2018

I have the same problem with our configuration. We are running a central web server (nginx) doing basic web application firewalling, HTTPS offloading and much more. It would be great if we could fix this error quickly so we can regain control over our network. Base URL is already set in the config file.

@MrXermon
Copy link
Contributor

Semms like there is already a solution:
https://community.librenms.org/t/solved-web-interface-broken-after-update/5377/5

@corny
Copy link
Contributor Author

corny commented Sep 12, 2018

That's just a workaround. I don't want a self signed certificate because the communication between proxy and LibreNMS is already secured via IPSec.

@laf laf closed this as completed Sep 12, 2018
@corny
Copy link
Contributor Author

corny commented Sep 12, 2018

@laf Why did you close this issue?

@murrant
Copy link
Member

murrant commented Sep 13, 2018

This issue has been closed as it isn't classed as anew device request.

For help please use our Discord server or the community site: http://docs.librenms.org/Support/FAQ/#faq3

@librenms librenms locked as off-topic and limited conversation to collaborators Sep 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants