[GH-ISSUE #124] SSL error - streams-nodes-messages do not load over https - behind a reverse proxy. #98

Closed
opened 2026-02-26 05:31:19 +03:00 by kerem · 1 comment
Owner

Originally created by @LaKing on GitHub (Aug 7, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/124

Simply nothing gets loaded, not even streams/nodes names.

No server-side error. The only error message I have is in the browser:
Uncaught ReferenceError: io is not defined Dpu9AEpcnQ7W5JDfgC4M?t=1407381974692&i=0:1
(anonymous function) Dpu9AEpcnQ7W5JDfgC4M?t=1407381974692&i=0:1

I tested following cases:
http <> log.io - OK
https <> ssl-enabled-log.io - OK
http <> proxy <> log.io - OK
https <> proxy <> log.io - NO-GO
https <> proxy <> ssl-enabled-log.io - NO-GO
Where the proxy translates from log.io's port to port 80/443, and handles the certificates.
In my case the proxy is Pound as a reverse proxy.

Can I be of assistance to resolve this issue?

Originally created by @LaKing on GitHub (Aug 7, 2014). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/124 Simply nothing gets loaded, not even streams/nodes names. No server-side error. The only error message I have is in the browser: Uncaught ReferenceError: io is not defined Dpu9AEpcnQ7W5JDfgC4M?t=1407381974692&i=0:1 (anonymous function) Dpu9AEpcnQ7W5JDfgC4M?t=1407381974692&i=0:1 I tested following cases: http <> log.io - OK https <> ssl-enabled-log.io - OK http <> proxy <> log.io - OK https <> proxy <> log.io - NO-GO https <> proxy <> ssl-enabled-log.io - NO-GO Where the proxy translates from log.io's port to port 80/443, and handles the certificates. In my case the proxy is Pound as a reverse proxy. Can I be of assistance to resolve this issue?
kerem closed this issue 2026-02-26 05:31:19 +03:00
Author
Owner

@msmathers commented on GitHub (Aug 7, 2014):

Unfortunately Log.io doesn't officially support reverse proxying at this time, when it is part of the roadmap we'll investigate more closely.

<!-- gh-comment-id:51504571 --> @msmathers commented on GitHub (Aug 7, 2014): Unfortunately Log.io doesn't officially support reverse proxying at this time, when it is part of the roadmap we'll investigate more closely.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/log.io-NarrativeScience-old#98
No description provided.