Thanks Mohammad S. AlMutairi
Its still not working
The problem is that the changes dont do anything . Everything is overidden
by local.cfg in /dspace.
When I have
dspace.ui.url = http://dspace7.lnec.pt:4000
I can access via the domain name
if I change that to an ip address in the local.cfg
I forgot to add... if you are trying to simply make the UI available on the
web, I'd highly recommend considering keeping the UI running on
"localhost:4000" and using a Proxy to respond at https://[domain name].
See our installation guide, step 8 "Add HTTPS support" for the Frontend
install:
Hi,
The problem may be that you forgot to change the "dspace.ui.url" setting
(on the backend) to include the domain name. When changing the URLs (from
IP to hostname), you have to ensure you update the URL settings in the
backend's "local.cfg" (both "dspace.server.url" and "dspace.ui.url")
The default install sends it to 4000
i never bothered to change it ...
Dont think it will influence my problem either way ?
On Monday, December 12, 2022 at 1:32:25 PM UTC alo...@gmail.com wrote:
> On Monday, December 12, 2022 at 3:18:33 PM UTC+3 jorge...@gmail.com wrote:
>
>> http://[domain
This is the config from /dspace/config/dspace.cfg
#
# DSpace Configuration
#
# NOTE: The DSpace Configuration File is separated into several sections:
# * General Configurations
# * UI Configurations
#--#
On Monday, December 12, 2022 at 3:18:33 PM UTC+3 jorge...@gmail.com wrote:
> http://[domain name]:4000/home
> gets me 500 Service Unavailable
>
Do you have any specific reason to run it on port 4000?. If you don't just
change port 4000 to port 80 and access it without having to write the port
Check your settings in local.cfg or dspace.cfg and config.prod.yml or post
them here.
On Monday, December 12, 2022 at 3:18:33 PM UTC+3 jorge...@gmail.com wrote:
> http://[ip]:4000/home works just fine.
> ITs integrated with my AD
> I can log in , browse , deposit , delete etc
>
> http://[domain
