Having trouble logging into openwrt - raspberry-pi

I just installed OpenWRT on my Raspberry PI but couldn't log in.
The port scan shows that ports 22, 23 and 53 are open, but I don't know the default SSH password (tried root/admin but that does not work) and telnet doesn't work either.
The image comes from the latest posts of OpenWRT: openwrt-brcm2708-sdcard-vfat-ext4.img.
Is port 80 supposed to be open and if it is not, what can I do about it?

First login to OpenWrt is different: telnet as root with no password until you set it. More here -> http://wiki.openwrt.org/doc/howto/firstlogin

Related

why are wekan calls to mongodb unable to connect?

I recently installed Manjaro and followed this tutorial: https://snapcraft.io/install/wekan/manjaro to install wekan. Everything went slicker than snot. I registered an account no issues, open the weken webgui at port 8080 without issue, create new lists and cards fine, but when I go to open the cards I create the connection to 127.0.0.1 is refused. Although it doesn't specify a port, I assume this is a call to the mongodb at the default port 27017, but I also opened up 28017 in the firewall.
Although mongo definitely seems to have been installed since I can see it is running, I can't find a mongod*.conf file on the system to verify the default ports.
This is the first time I used “snap” to install anything, and because it all went so seamlessly I have no clue where to start looking to find the issue. Is there a utility in snap where I can find out exactly what was installed to support wekan (webserver, database, etc.) that I can start checking into as potentials sources of issue. Thks.

access windows 10 localhost from mac running parallels 14

How can I access the localhost of windows 10 from my mac.
I'm running parallels 14 from my mac.
If I look at my hosts file it looks like this:
10.211.55.3 windows-10.shared windows-10 #prl_hostonly shared
BUt I cannot curl windows 10 or 10.211.55.3 windows-10.shared
In configuration / setting of Window Parallels, select tab "Hardware" and look for Network. Make sure source option is selected as Shared Network (Recommended).
In Macbook, open System Preferences > Network, you will see IP address. Copy this IP address, you will need it to run as host for your local server.
Run local server with the host of the copied IP address. Use the same ip address to access your local server in Window Parallels' browsers.

EasyPHP Devserver 17

Is there an easier way to connect to my localhost than using my the whole directory structure
e.i.:
file:///C:/Program%20Files%20(x86)/EasyPHP-Devserver-17/eds-binaries/httpserver/apache2425vc11x86x180404190153/htdocs/CCB%20Waterloo/index.html.
Still need help,
Your suggestion for http://localhost/CCB%20Waterloo/index.html doesn't work get refused to connect
(This site can’t be reached
localhost refused to connect.
Search Google for localhost CCB Waterloo index
ERR_CONNECTION_REFUSE)
Not used to the newer version. Have an error with dashboard that MSVCR100.dll not found. Then the Easy PHP server at 127.0.0.1 refused to connect.
For your MSVCR problem, fisrt, read this : http://www.easyphp.org/faq_devserver.php#collapse001
And when EasyPHP Devserver is running properly, open tyour file with : http://127.0.0.1/CCB%20Waterloo/index.html. If the port is different from 80, 88 for example, use http://127.0.0.1:88/CCB%20Waterloo/index.html

Raspberry Pi VNC fail connection

I face a problem that I can ping to correct IP address, it have no loss. And also I use nmap ping the pi address, and I get it correctly. Then I using VNC viewer to try access to pi, but it always show up "The connection was refused by the host computer"
Did u all have any idea ?
Your problem indicates that your Raspberry Pi was reached by the connection attempt, but that no service was running on the relevant port and hence the connection was refused. I think, this is because the VNC service is not running on your Raspberry Pi.
Update 1
Raspbian now comes with the server by default thanks to a partnership with RealVNC, it just needs to be enabled.
Original
You must enable VNC Server on your Raspberry Pi using terminal
sudo apt-get update
sudo apt-get install realvnc-vnc-server
or you can also enable VNC Server on the command line using the sudo raspi-config command.
Advanced Options->VNC:Yes
Now you can connect to the VNC Server using a application such as VNC Viewer.
I have been having this issue with my Raspberry Pi Zero W even though it worked perfectly beforehand. This page https://www.realvnc.com/en/connect/docs/raspberry-pi.html should help.
I ran vncserver in a ssh window after verifying the interface settings in raspi-config.
It started the VNC Server and gave me the VNC Server catchphrase and the IP address with Port Number as shown in the photo linked below.
vncserver output
After running that command I was able to get the VNC Viewer on my windows machine to connect to the pi.
I then ran sudo systemctl enable vncserver-x11-serviced.service in the ssh window so that it would start automatically on subsequent reboots.
I've had this same problem but found a different reason. I found three ways to get around this error message.
Plug a mouse or keyboard into the Raspberry Pi zero, waking up the screen and the VNC connection.
Wait about 5 - 10 minutes which is the amount of time for the screen saver to kick in which seems to wake up VNC connection. but don't wait to long other wise run this command to get things going via ssh "systemctl start vncserver-x11-serviced.service".
I am hoping the new update they just published will fix this problem. I don't see this as much with the Raspi B3+ as with the Zero H.
The last was plug in both monitor and mouse and that for sure fixes the VNC issues but defeats the headless connection. It seems that running headless and the screen/saver are somehow related but just not smart enough to figure it out.
For people using newer version of Raspberry, VNC option is found under:
Config>Interface Options
pinging to any service will only tells us that whether the server is currently listening on that port or not. It will not tell you the possible result to connection request asked by client.
It seems that, you have installed VNC server but not started it properly. Use this command to start it...
# vncserver start
Also recheck the port number is correct or not.
With the Rasp Pi 4 - had connecting fail after rebooting both the server and client (both Rasp Pi 4s).
Took a while to realize that I have two clients: One named "VNC Client", the other "VNC Viewer for Google Chrome".
The former works, the latter doesn't.

Using "http://localhost" instead of "http://xx.xx.xx.xx" on iPod on WAMP

I am running Windows 7 and use my iPod Touch to access my localhost sites for testing purposes on WAMP.
I can browse my localhost sites by navigating to my machine IP in Safari on my iPod like so: http://10.0.0.100
I would like to know if it is at all possible to use http://localhost instead, and how I can accomplish that.
Thank you very much!!
Basically, localhost refers to 127.0.0.1 refers to the loop back ip which is the ipod itself so it's not possible unless you change [localhost to resolve to machine IP which is in this case 10.0.0.100] in the (DNS / hosts file) your ipod is using to resolve domain names in your connection settings and I don't recommend that.
Following are the steps needed to change the hosts file in your ipod (I warned you already this is not a good thing unless you know what are you doing)
source: https://discussions.apple.com/thread/2801892?start=0&tstart=0
Simple solution:
the hostfile is located at: /etc/hosts
To edit this file you need to SSH into your device, If you know how to do this directly just use vi, or nano to edit the file. From windows use WinSCP to access the file system via FTP(SSH). Then simply navigate to /etc/hosts download the file to your desktop, right click and open it with note pad, add your resolver to the last line "192.168.0.100 testserver", save, and replace the original file with the new one.
/etc/host -- example config
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
192.168.0.100 testserver
*To SSH into an ipod it must have OpenSSH installed, usually this requires a jailbreak.