Not quite sure what I am missing here.
My instance name is default and the URL im using is http://default
my localhost/r/test is working
Not sure why im getting these 301 errors when trying to log in with internal user.
I've completed these 3 steps
Solved! Go to Solution.
Views
Replies
Total Likes
I was able to resolve this. The documentation on the first start of the has you start then stop tomcat. And I never restarted tomcat after that. Simply running nlserver start web did the trick for http://localhost. Which then I was able to go in and create my other instances.
Hi@David_Loyd - check the URL you have set up in the client (click LocalHost in the login window). The error is trying to access "https://www.adobe.com/nl/jsp/soaprouter.jsp" - so your URL on your connection is likely set to "www.adobe.com"
The URL should be pointing to your localhost instance or 127.0.0.1
Cheers
Darren
Views
Replies
Total Likes
Im not sure where www.adobe.com is coming from. my instance name is "default". neither my serverConfig or config-default have that adobe.com url.
I tried 127.0.0.1 and got this error.
INT-150012 The HTTP query returned a 'Internal Server Error' type error (500)
------
SOP-330021 Communication error with server: please make sure it is configured correctly.
HTTP code 500
'WEB-530007 Error relaying '/nl/jsp/soaprouter.jsp' to URL 'http://localhost:8080/nl/jsp/soaprouter.jsp'.'.
------
Views
Replies
Total Likes
@David_Loyd Your original post in this thread showed that your localhost is running on port 80 (http://localhost/r/test) - try removing the port 8080 in your client connection
Cheers
Views
Replies
Total Likes
when i connect to http://Localhost i'm still getting a relay error.
When I run pdump from the CLI i see the system running.
Views
Replies
Total Likes
Seems like you have missing services?
Can you run the following command
nlserver monitor -missing
Apache doesnt seem to be running?
More troubleshooting commands on this doc https://experienceleague.adobe.com/docs/campaign-classic/using/monitoring-campaign-classic/productio...
Views
Replies
Total Likes
I was able to resolve this. The documentation on the first start of the has you start then stop tomcat. And I never restarted tomcat after that. Simply running nlserver start web did the trick for http://localhost. Which then I was able to go in and create my other instances.
Right, so you had missing services as per your dump web@default was not running which means it had to be restarted
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies