See the guide here for finding the underlying error that is causing your 
DSpace user interface not to 
load. 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Unfortunately, there are a variety of reasons why the UI might not be able 
to communicate with the backend, so you have to find the underlying error 
message to determine which scenario you are encountering.  It almost always 
is a configuration problem, but it may be a configuration issue on the 
frontend or on the backend.  See also this list of "common issues" most of 
which can result in the UI being unable to 
load: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues

Once you find the underlying error message, if you cannot find it listed in 
the Common Installation Issues, you can send it to this mailing list and we 
can help.

Tim

On Thursday, January 20, 2022 at 10:34:11 AM UTC-6 [email protected] wrote:

> It's a common issue caused by how you setup DSpace. localhost usually 
> configured if you can access this URL locally or using a tunneled 
> connection for development/testing purposes.
>
> Stackoverflow poster is using Windows server 2012. Are you using Windows? 
> or Linux?.
>
> On Thursday, January 20, 2022 at 3:49:18 PM UTC+3 [email protected] 
> wrote:
>
>> hello 
>> for a few days now i am having a problem in frontend installation  just 
>> like what is mentioned here 
>> https://stackoverflow.com/questions/68811629/dspace-does-not-load 
>>
>> my environment  settings are 
>> export const environment = {  
>>   // The "ui" section defines where you want Node.js to run/respond. It 
>> often is a *localhost* (non-public) URL, especially if you are using a 
>> Proxy.
>>   // In this example, we are setting up our UI to just use localhost, 
>> port 4000.
>>   // This is a common setup for when you want to use Apache or Nginx to 
>> handle HTTPS and proxy requests to Node on port 4000
>>   ui: {
>>       ssl: false,
>>       host: 'localhost',
>>       port: 4000,
>>       // NOTE: Space is capitalized because 'namespace' is a reserved 
>> string in TypeScript
>>       nameSpace: '/'
>>   },
>>   // This example is valid if your Backend is publicly available at 
>> https://api.mydspace.edu/server/
>>   // The REST settings MUST correspond to the primary URL of the 
>> backend. Usually, this means they must be kept in sync
>>   // with the value of "dspace.server.url" in the backend's local.cfg
>>   rest: {
>>       ssl: false,
>>       host: 'localhost',
>>       port: 8080,
>>       // NOTE: Space is capitalized because 'namespace' is a reserved 
>> string in TypeScript
>>       nameSpace: '/server'
>>   }
>> };
>>
>> and when i try 
>> yarn config:check:rest
>> the response is 200
>>
>> i tried to reinstall every thing and it did not work either . 
>> can some one help me please 
>>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/af76516e-c69f-41ce-b39d-fadb59b4b83an%40googlegroups.com.

Reply via email to