I'm trying to setup github with netbeans using the https path. I go to the push menu and enter the info it needs for repo URL and username/password but when I hit next it just says "Cannot connect to the remote repository at my repository" I've done a little bit of research but nothing has helped so far.
I tried reinstalling netbeans but i'm getting the same error. I should also mention that it works just fine on my laptop.
It appears that netbeans has no network connectivity. It fails to check for updates as well. I tried disabling anti-virus and firewall but neither helped. My computer definitely has internet. I successfully checked updates on my laptop which was on the same network.
The main error that I keep seeing is Unexpected end of file from server whenever I check for updates or test connection in options.
Here is a link to the relevant log: Pastebin LogFile
Found the culprit. Apparently Covenant Eyes is blocking all network connectivity within NetBeans. After reinstalling Covenant Eyes it appears to working now. For now i'm going to mark this as solved unless something else comes up.
Related
After succesfully deployment via Github repo of my Spring boot Application in Azure's App Service i have still "Hey java developers!" page, i tried do this via Github and Github Actions, Github and Kudu, FTP, but result is allways the same. I'm out of ideas.
UPDATE
Today, I try again. I disconnect connection. And try to reconnect, I saw build area like below.
After Action completed, it works.
So I suggest you disconnect and reconnect to solve the problem.
PRIVIOUS
According to your description, I personally tested one side and your problem reappeared.
My troubleshooting steps:
First create a default page for webapp. (Under windows, it fails, indicating that this is not).
Deploy the webapp under linux and find that everything is normal.
From the Action on github, it was found that there should be a problem with the build in the deployment under windows.
In conclusion:
It is recommended to use linux to deploy webapp. As for the deployment failure under windows, it is recommended to raise a support ticket for help.
My test result.
Under Linux, after build action, we can see app.jar file under wwwroot folder.
I also move it to windows webapp, it doesn't work.
I am having difficulty getting Cognito registration and login to work for my app in Android Studio using this sample. When I attempt to log in via the simulator, the app works for a few seconds, then displays an error message: "Unable to execute HTTP request: Unable to resolve host 'cognito-idp.us-east-1.amazonaws.com': No address associated with hostname". This same error is the only error that appears in the console. I have seen similar questions and tried solutions such as checking to ensure my app has the permissions android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE, but the error persists. It also doesn't seem to be a network issue. I have updated to the latest version of the Android SDK as well as the AWS SDK, and the problem persists.
I currently I have a Cognito user pool set up which works properly for login on the iOS version of my app. Following the instructions in the readme for the sample code, I added an app to my existing user pool, and then copied and pasted the newly generated app client ID and app client secret into AppHelper.java for clientId and clientSecret respectively. I also set userPoolId to the ID listed for my user pool under "pool details" in the Cognito conosle, and cognitoRegion to US East, since this is the region of my user pool. I noticed that there was no need for me to set the pool name, as there was in the iOS version, so I'm wondering if that's something I need to do.
Sorry if this counts as a duplicate, but I wanted to post a question with the exact error message I encountered and the steps I took, and I'm wondering if someone has managed to get this specific sample working and what I should do.
The problem has been resolved, but unfortunately I'm not quite sure what fixed it since I didn't change anything in the code. All I did was install an update, so anyone with a similar problem should probably ensure that all SDKs used in the sample are properly updated, along with the simulator. It's also worth noting that I was using a different network than in my previous tests, so it's possible that it was a network issue after all.
I had the same issue.
The issue occurred when I used a VPN with emulator to test my program. The reason was that the internet connection in the emulator was too slow when connecting through a VPN.
This could also happen if your internet connection is not strong enough.
The solution is, use a real android device to test your code, if your internet connection is not good enough.
More info: https://github.com/aws-amplify/aws-sdk-android/issues/567
After running app-engine java project multiple times in eclipse, app-engine local server doesn't work. I am getting error "This webpage is not available" in Google chrome. But eclipse console says that "dev App Server is now running". But using dev_appserver.cmd works fine, it is too difficult when developing the project. Any ideas to solve this?
PS: rerunning is done after stopping the current execution of the server.
Choose 'Automatically select an unused port' in debug configuration.
Local server will start every time on different port, but it should solve your problem.
try to change the configuration by "run as" or "debug as" and check server and port no.
Also ensure that in Windows>>preference>>java>>jre a path to jdk (not jre) is selected.
Please provide more details of the problem if it is still there.
I posted this error here cuz it has been disturbing me for long time whenever i try to connect to my web api from my j2me application.I just would like to share this if somebody has same problem as me.
When this error happened to me, it was because my web server (tomcat) was not running. Make sure that your web server is up and running then try again.
my solution to this error is i changed in host file which is located at C:\Windows\system32\drivers\etc\ and i opened the ip that i m trying to call.
the other attempt i did if this one is not working is check the instances whether they are already run or not. This is also one option which really did solve the TCP open error.
I am having issues with RAD7.
My server will not start for me today. I am working from home and connected to the VPN. Everything works except my server in RAD. It worked fine yesterday in work and had previously worked when I was at home but that was a few weeks ago.
Are there any settings that I should look out for? I have disabled my proxy settings in RAD and turned off everything in my firewall. I can ping all the DBs that the server is connecting to.
I have even removed all the projects from the server and it will still not start. It keeps trying and then times out after 300s.
Any suggestions?
I got a similar error while Starting WebSphere Commerce server v7. This error in my case was caused by me increasing the Maximum Heap size to 2096. I reduced the heap size to 1536 and it worked. None of the errors/trace files indicated this problem.
I had this problem too. Double-click on the server to open the server 'OVERVIEW' tab/view. Scroll down to the section under 'Optimize server start for development:'; uncheck 'Start server with a generated script'. This worked for me. good luck.
I have had this problem once before. I wasn't able to figure out what went wrong, but deleting that server and creating a new one (under Window -> Preferences -> Server -> WebSphere Application Server) fixed the problem.
Re the file not found exception. Make sure the directory path in Windows is of the CoRRectCase, e.g., GALFTGA342130Node01Cell-> galftga342130Node01Cell. I've encountered this on various RAD installations.
With reference to your following comment -
I looked at startserver.log and I saw a file not found exception for this file C:\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\config\cells\GALFTGA342130Node01Cell\nodes\GALFTGA342130Node01\serverindex.xml. I checked and the file exists but when I try to open it, I get told access denied.
this link may help you in understanding the problem. it says -
This is a permissions issue caused by the automatic port detection routine. If any profiles already exist and were created as a different user, the port detection routine will try to open the serverindex.xml file in each profile and will fail.
You should set appropriate permissions for your user.
after working several hours in my case I found the solution I hope it works for you ; change my JDK to alternate JRE