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

Got broken after installed #528

Open
ptr1226 opened this issue Apr 21, 2023 · 3 comments
Open

Got broken after installed #528

ptr1226 opened this issue Apr 21, 2023 · 3 comments

Comments

@ptr1226
Copy link

ptr1226 commented Apr 21, 2023

System Info

  • PHP Version: 7.3
  • XBackBone Version: Latest (downloaded today)
  • Webserver: Apache
  • Database backend: SQLite

Describe the bug

The website is just fully broken after i installed, i didnt even touch nothing, the installer was fine tho.

image
image

To Reproduce
Steps to reproduce the behavior:

  1. Install it

Logs
XBackBone and/or webserver logs.
log-2023-04-21.txt

@patryck507
Copy link

had the same problem, using Nginx Proxy Manager depeneds on http/https got it fixed after trying like 300 times

@chikovanreuden
Copy link

i have the same issue.
In my case i was able to track down the issue easily...

i got myself a nice .app domain.
The usage the HTTP Protocol with the .app-TLD is not allowed (see https://icannwiki.org/.app and https://blog.google/technology/developers/introducing-app-more-secure-home-apps-web/). Browsers and Mobile Appications Frameworks with an Web Engine require anything to be served over HTTPS, encrypted and secure.

The Problem: this Project somehow decides to serve static Content over HTTP and anything else via HTTPS.

Any Browser complains with "Mixed-Content" -> serving on HTTP and HTTPS where only HTTPS is allowed.

@Manriel
Copy link

Manriel commented May 16, 2024

The Problem: this Project somehow decides to serve static Content over HTTP and anything else via HTTPS.

Make sure your config.php parameter "base_url" is corresponded http or https protocol and correct domain name on which app is served.

Im getting the same issue when I open the app via https but base_url is containing http, or vice versa, I open the app using http proto, but base_url is containing https proto, served with outdated/invalid cert.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants