Hi,
I can verify that you *MUST* enable HTTPS on the backend if you want to
access the backend via an IP address. Without HTTPS, it's possible the
basics will work, but I know that you will not be able to login to the
system until you enable HTTPS.
It's only possible to (easily) run DSpace
I'm not part of the Dspace development team, just a user. So I'm not *sure
*that
you need to enable the https support but I believe is the right direction
to fix the problem.
Regarding the logs, I'll try to help you as much as I can if you send them.
The paths for the logs are on this link
Thank you for your guidance,
are you sure that, if i want to access dspace from the ip address i need to
enable https ?
and could you please help me if i send you the logs file ? actually i am
new in dsapce that why and please guide me where i can collect the logs for
you ? I mean which directory
I'm linking both related posts for this same user for future searchers.
https://groups.google.com/g/dspace-tech/c/qORZonB_AYw/m/oBPhbTZJ
On Friday, February 17, 2023 at 5:04:09 PM UTC+3 Agustín Alfieri wrote:
> I may be wrong, but I'm pretty sure that it doesn't matter whether is from
> the
I may be wrong, but I'm pretty sure that it doesn't matter whether is from
the IP or the domain name, as long as you want to access Dspace from
anything that's *not localhost* you must enable HTTPS support on the
backend. I suggest you take a look at this.
Furthermore, you need to understand
Hi!
The first thing that comes to mind is that maybe you didn't enable HTTPS
support for the backend, as the wiki says "*If you want to run DSpace in
Production, you MUST run the backend with HTTPS support* (otherwise logins
will not work outside of your local domain)."
If this is not the
